| 1 | Opening of the meeting | |
|---|---|---|
| R2-2202057 | - | - |
| 2.1 | Approval of the agenda | |
| R2-2200000 | Agenda for RAN2#116bis-e | Chairman |
| 2.2 | Approval of the report of the previous meeting | |
| R2-2200001 | RAN2#116-e Meeting Report | MCC |
| R2-2201970 | RAN2#116-e Meeting Report | MCC |
| 2.4 | Others | |
| R2-2200002 | RAN2 Handbook 01-22 | ETSI MCC |
| R2-2201693 | RAN2 planning 2022 H1 | Chair |
| 3 | Incoming liaisons | |
| R2-2200063 | LS on NAS procedure not subject to UAC (C1-217227; contact: Apple) | CT1 |
| R2-2200070 | Reply LS on RMSI reception based on non-zero search space (R1-2112765; contact:OPPO) | RAN1 |
| R2-2200072 | LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#107-e (R1-2112778; contact: NTT DOCOMO) | RAN1 |
| R2-2200079 | Reply LS on PDCCH Blind Detection in CA (R1-2112833; contact: Huawei) | RAN1 |
| R2-2200087 | Reply LS on initial state of elements controlled by MAC CEs (R1-2112860 | RAN1 |
| R2-2200088 | Reply LS on UL skipping with LCH prioritization (R1-2112862; contact: vivo) | RAN1 |
| R2-2200102 | Reply LS to RAN2 on the misalignment in SRS configuration (R3-216009; contact: Samsung) | RAN3 |
| R2-2200106 | Reply LS on inter-MN handover without SN change (R3-216165; contact: Huawei) | RAN3 |
| R2-2200107 | Reply LS on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems (R3-216196; contact: Nokia) | RAN3 |
| R2-2200111 | Reply LS on Guidelines on Port Allocation for New 3GPP Interfaces (R3-216233; contact: Ericsson) | RAN3 |
| R2-2200114 | Reply LS on signalling SN initiated release of SCG (R3-216236; contact: Ericsson) | RAN3 |
| R2-2200116 | LS on Rel-16 updated RAN4 UE features lists for LTE and NR (R4-2118536; contact: CMCC) | RAN4 |
| R2-2200119 | LS on Signalling of PC2 V2X intra-band concurrent operation (R4-2119992; contact: Xiaomi) | RAN4 |
| R2-2200121 | LS on PEMAX for NR-V2X (R4-2120047; contact: Huawei, CATT) | RAN4 |
| R2-2200134 | LS UE capability for supporting single DCI transmission schemes for multi-TRP (R4-2120652; contact: Apple) | RAN4 |
| R2-2200136 | LS on configuration of p-MaxEUTRA and p-NR-FR1 (R5-217995; contact: Huawei) | RAN5 |
| R2-2200137 | LS response to ETSI TC LI on Location Services for Drones (RP-213674; contact: Ericsson) | RAN |
| R2-2200164 | LS on Energy Efficiency as guiding principle for new solutions (SP-211621; contact: Nokia) | SA |
| 4 | EUTRA corrections Rel-15 and earlier | |
| R2-2201532 | Discussion on handling QoE configuration in full configuration | Google Inc. |
| 6 | Rel-16 NR Work Items | |
| R2-2200034 | Summary [POST116-e][710][V2X/SL] PDCP/RLC Entity Maintenance for SL-SRBs (CATT) | CATT |
| R2-2200035 | Corrections on MAC filtering issue for the first unicast PC5-S signalling | CATT |
| R2-2200036 | Corrections on RLC entity establishment issue for the first unicast PC5-S signalling | CATT |
| R2-2200037 | Corrections on PDCP entity establishment issue for the first unicast PC5-S signalling | CATT |
| R2-2200305 | Handling of ServingCellConfigCommon | Qualcomm Incorporated |
| R2-2200439 | Draft reply LS on PEMAX for NR-V2X | Qualcomm Finland RFFE Oy |
| R2-2201539 | Correction on LTE UE RLF Report | China Telecommunications, CATT |
| R2-2201540 | Correction to RRC reconfiguration for IAB | Google Inc. |
| 8.0.1 | RRC | |
| R2-2200081 | LS on Rel-17 MAC-CE impacts (R1-2112842; contact: Nokia) | RAN1 |
| R2-2201172 | Rel-17 ASN.1 review plan | Ericsson |
| R2-2201487 | Draft CR for SetModifyRelease structure (38.331) | Ericsson |
| R2-2201488 | Set Modify Release structure | Ericsson |
| 8.0.2 | UE capabilities | |
| R2-2200091 | LS on updated Rel-17 RAN1 UE features list for NR (R1-2112903; contact: NTT DOCOMO, AT&T) | RAN1 |
| R2-2200095 | LS on updated Rel-17 LTE and NR higher-layers parameter list (R1-2112977; contact: Ericsson) | RAN1 |
| R2-2200307 | Discussion on BWP operation without bandwidth restriction | Qualcomm Incorporated |
| R2-2200458 | Release-17 UE capabilities based on R1 and R4 feature lists (TS38.306) | Intel Corporation |
| R2-2200459 | Release-17 UE capabilities based on R1 and R4 feature lists (TS38.331) | Intel Corporation |
| R2-2201489 | Allowing FRx/xDD differentiation on UE capabilities | Ericsson, Samsung |
| R2-2201653 | Release-17 UE capabilities based on R1 and R4 feature lists | Intel Corporation |
| R2-2201654 | Release-17 UE capabilities based on R1 and R4 feature lists | Intel Corporation |
| R2-2201907 | Release-17 UE capabilities based on R1 and R4 feature lists | Intel Corporation |
| R2-2201908 | Release-17 UE capabilities based on R1 and R4 feature lists | Intel Corporation |
| 8.0.3 | Gaps Coordination | |
| R2-2200221 | Joint discussion for measurement gaps | Intel Corporation |
| R2-2200292 | Discussion on gaps coordination | Huawei, HiSilicon |
| R2-2200588 | Discussion on Gap coordination | vivo |
| R2-2201057 | Commonalities with measurement gaps in Rel-17 | Nokia, Nokia Shanghai Bell |
| R2-2201109 | Discussion on gap features | Apple |
| R2-2201238 | Discussion on gap coordination | MediaTek Inc. |
| R2-2201565 | Gaps coordination | Ericsson |
| R2-2201904 | Report of [AT116bis-e][018][NR17] Gaps Coordination (Mediatek) | MediaTek Inc. |
| 8.1.1 | Organizational | |
| R2-2200022 | NR MBS open issue list | Huawei, HiSilicon |
| R2-2200066 | Reply LS on MCCH change notification (R1-2112646; contact: BBC) | RAN1 |
| R2-2200085 | LS on MTCH scheduling window (R1-2112850; contact: BBC) | RAN1 |
| R2-2200101 | Reply LS on MBS broadcast service continuity and MBS session identification (R3-215977; contact: Huawei) | RAN3 |
| R2-2200108 | LS on handover from MBS supporting node to MBS non-supporting node (R3-216222; contact: Lenovo) | RAN3 |
| R2-2200141 | Reply LS on maximum number of MBS sessions that can be associated to a PDU session (S2-2109171; contact: Ericsson) | SA2 |
| R2-2200142 | LS on MBS broadcast service continuity and MBS session identification (S2-2109187; contact: Huawei) | SA2 |
| R2-2200147 | Reply LS on Feedback on data forwarding solutions for MBS (S2-2109351; contact: Nokia) | SA2 |
| R2-2201729 | 38.323 running CR for NR MBS | Xiaomi Communications |
| R2-2201813 | 38.321 running CR for NR MBS | OPPO |
| R2-2201971 | 38.304 running CR for NR MBS | CATT |
| 8.1.3.1 | General | |
| R2-2200021 | Untreated proposals from offline discussion: [AT116-e][051][MBS] CP continuation | Huawei, HiSilicon |
| R2-2200234 | Open Issues on Broadcast Service Continuity | CATT, CBN |
| R2-2200235 | Open Issues on Multicast Service Continuity | CATT, CBN |
| R2-2200382 | Discussion on MBS interesting indication for delivery mode 2 | OPPO |
| R2-2200385 | Open issues multicast activation and service continuity of broadcast | OPPO |
| R2-2200386 | Discussion on PTM activation-deactivation for MBS | OPPO, CMCC, ZTE, Huawei, HiSilicon, SJTU, NERCDTV, Lenovo, Motorola Mobility, Spreadtrum, TCL, Xiaomi, CATT, MediaTek, Qualcomm, Kyocera, Apple, Sharp, China Unicom, CBN, China Telecom, FGI, APT, InterDigital |
| R2-2200398 | Broadcast Service Continuity | Samsung |
| R2-2200532 | NR MBS control signaling aspects | Qualcomm Inc |
| R2-2200534 | NR Multicast loss-less HO enhancements with service continuity | Qualcomm Inc |
| R2-2200538 | Clarification on details of MCCH change notification via DCI | Futurewei |
| R2-2200539 | Discussion on MBS with conditional handover | Futurewei |
| R2-2200540 | Discussion on priority reselection based on SIBx of the neighbor cells | Futurewei |
| R2-2200576 | Service continuity for multicast mode | TD Tech, Chengdu TD Tech |
| R2-2200577 | Service continuity for broadcast mode | TD Tech, Chengdu TD Tech |
| R2-2200641 | Discussion on Multicast service continuity during mobility | Spreadtrum Communications |
| R2-2200728 | Miscellaneous Aspects of MBS Provisioning | Nokia, Nokia Shanghai Bell |
| R2-2200756 | Service Continuity for handover from MBS Supporting Node to MBS non-Supporting Node | Lenovo, Motorola Mobility |
| R2-2200759 | MII and BWP related configuration | Lenovo, Motorola Mobility |
| R2-2200785 | MBS Mobility | Nokia, Nokia Shanghai Bell |
| R2-2200816 | MBS service continuity and notification for multicast | Huawei, HiSilicon |
| R2-2200817 | MBS service continuity for broadcast | Huawei, HiSilicon |
| R2-2200828 | Mobility and Service continuity for NR Multicast | MediaTek inc. |
| R2-2200857 | Discussion on Mobility with Service Continuity | CMCC |
| R2-2200858 | Discussion on MII issues | CMCC |
| R2-2200880 | Broadcast Service Continuity | Nokia, Nokia Shanghai Bell |
| R2-2200905 | UE based PTM to PTP switch | Sony |
| R2-2200978 | Multicast Service Continuity Aspects | Ericsson |
| R2-2200980 | Broadcast Service Continuity | Ericsson |
| R2-2200982 | Broadcast Notifications | Ericsson |
| R2-2201118 | Control plane aspects of MBS | Apple |
| R2-2201175 | Multicast service continuity and discussion on RAN3 LS | Intel Corporation |
| R2-2201176 | Broadcast service continuity | Intel Corporation |
| R2-2201244 | Remaining issues of MBS Interest Indication | Kyocera |
| R2-2201245 | Remaining issues of cell reselection procedure for MBS | Kyocera |
| R2-2201256 | Mobility with non-supporting nodes | Nokia, Nokia Shanghai Bell |
| R2-2201258 | Mobility for NR MBS | vivo |
| R2-2201291 | MCCH information acquisition | LG Electronics |
| R2-2201292 | Remaining issues on group notification for multicast session | LG Electronics |
| R2-2201365 | Multicast Service Continuity | Samsung |
| R2-2201370 | Remaining issues for MII | LG Electronics France |
| R2-2201382 | Remaining issues of the multicast notification | Xiaomi Communications |
| R2-2201411 | UE initiated mode switch for Multicast | ZTE, Sanechips, Kyocera, InterDigital, CMCC, OPPO |
| R2-2201412 | Mobility Between MBS Supporting Nodes | ZTE, Sanechips |
| R2-2201413 | RAN1 related issues in NR MBS | ZTE, Sanechips |
| R2-2201634 | MBS Mobility | Nokia, Nokia Shanghai Bell |
| R2-2201636 | lossless handover for PTM | InterDigital |
| R2-2201637 | PTM activation and deactivation | InterDigital |
| R2-2201832 | Report of [AT116bis-e][021][MBS] MBS Interest Indication Open Issues | CMCC |
| R2-2201837 | Report of [AT116bis-e][022][MBS] Cell reselection Prioritization | CATT |
| R2-2201851 | [Report of] e-mail discussion: [AT116bis-e][020][MBS] Multicast Start (LGE) | LG Electronics Inc. |
| R2-2201852 | [Report of] e-mail discussion: [AT116bis-e][023][MBS] MCCH (LGE) | LG Electronics Inc. |
| R2-2201880 | Report of [AT116bis-e][019][MBS] Multicast Handover and related reconfigurations (QC) | Qualcomm |
| 8.1.3.2 | RRC 38331 | |
| R2-2200236 | Open Issues on Common RRC Aspects | CATT |
| R2-2200356 | Miscellaneous MBS L3 open issues | Intel Corporation |
| R2-2200399 | Discussion on MBS RRC issues | Samsung |
| R2-2200578 | Discussion on L3 open questions for NR MBS | TD Tech, Chengdu TD Tech |
| R2-2200640 | Discussion on Multicast activation notification | Spreadtrum Communications |
| R2-2200775 | Discussion on receiving MBS under Scell | Lenovo, Motorola Mobility |
| R2-2200814 | 38.331 running CR for NR MBS | Huawei, HiSilicon |
| R2-2200815 | Discussion on RRC Running CR update with L1 parameters | Huawei, HiSilicon |
| R2-2200818 | Discussion on RRC parameters for MCCH and MTCH | Huawei, HiSilicon |
| R2-2201119 | Open issues for MBS RRC Running CR | Apple |
| R2-2201120 | L1 configuration for MBS | Apple |
| R2-2201259 | Discussion on MBS Open Issues for RRC CR | vivo |
| R2-2201260 | Supporting CFR Case E for RRC IDLE and INACTIVE UE | vivo |
| R2-2201829 | 38.331 running CR for NR MBS | Huawei, HiSilicon |
| R2-2201830 | LS on MBS issues | RAN2 |
| R2-2201838 | Report of [AT116bis-e][025][MBS] CFR Case E (vivo) | vivo |
| R2-2201861 | Report of offline: [AT116bis-e][024][MBS] RRC Miscellaneous | Huawei, HiSilicon |
| 8.1.3.3 | UE capabilities | |
| R2-2200237 | Discussions on NR MBS UE Capabilities | CATT |
| R2-2200357 | UE capabilities for Rel-17 MBS | Intel Corporation |
| R2-2200400 | UE capabilities for MBS | Samsung |
| R2-2200531 | MBS UE capability for supporting MRBs | Qualcomm India Pvt Ltd |
| R2-2200579 | UE capabilities for NR MBS | TD Tech, Chengdu TD Tech |
| R2-2200819 | Discussion on UE capabilities for MBS | Huawei, HiSilicon |
| R2-2200827 | Discussion on UE capability for NR MBS | MediaTek inc. |
| R2-2200874 | RAN2 UE Feature List for NR MBS | CMCC |
| R2-2200906 | MBS BWP UE capability and MBS resources | Sony |
| R2-2200979 | MBS Capabilities | Ericsson |
| R2-2201261 | Discussion on UE capabilities for MBS | vivo |
| R2-2201380 | Discussion on MBS support on MRDC | Xiaomi Communications |
| R2-2201384 | UE capability for ROHC and EHC | Xiaomi Communications |
| R2-2201865 | [AT116bis-e] [026][MBS] UE capabilities (MediaTek) | MediaTek |
| 8.1.4 | User Plane (MAC, PDCP) | |
| R2-2200238 | Consideration on UP Remaining Issues of MBS | CATT |
| R2-2200314 | Consideration on MBS power saving | Shanghai Jiao Tong University |
| R2-2200346 | Discussion on user plane open issues | Huawei, HiSilicon |
| R2-2200358 | Remaining issues of MBS user plane | Intel Corporation |
| R2-2200383 | Discussion on Header Compressionfor MBS | OPPO |
| R2-2200384 | Discussion on open issues in MAC running CR | OPPO |
| R2-2200533 | NR Multicast DRX aspects | Qualcomm India Pvt Ltd |
| R2-2200541 | L2 ARQ by PDCP for PTM | Futurewei, Qualcomm Inc., Intel, Kyocera, NEC, Samsung, Ericsson |
| R2-2200580 | Open issues for user plane for NR MBS | TD Tech, Chengdu TD Tech |
| R2-2200722 | MBS Reliability | Nokia, Nokia Shanghai Bell |
| R2-2200735 | Keeping UE in the same active BWP during multicast session | ASUSTeK |
| R2-2200757 | Remaining issues on multicast DRX | Lenovo, Motorola Mobility |
| R2-2200758 | Discussion on initial value of HFN | Lenovo, Motorola Mobility |
| R2-2200825 | Discussion on initial HFN and PDCP state variables | MediaTek inc. |
| R2-2200826 | Discussion on DRX related issues for MBS | MediaTek inc. |
| R2-2200829 | Remaining issues of PTP PTM switch | MediaTek inc. |
| R2-2200859 | Discussion on MAC remaining issues | CMCC |
| R2-2200860 | Discussion on PDCP remaining issues | CMCC |
| R2-2200981 | Aspects on Scheduling | Ericsson |
| R2-2201121 | Open issues for MAC Running CR | Apple |
| R2-2201262 | Remaining UP issues for Rel-17 MBS | vivo |
| R2-2201354 | MBS 38.323 remaining issue | TCL Communication Ltd. |
| R2-2201366 | User Plane Aspects for MBS | Samsung |
| R2-2201381 | Remaining issues of MBS PDCP | Xiaomi Communications |
| R2-2201383 | Slow-moving PDCP reception window issue | Xiaomi Communications |
| R2-2201414 | DRX for NR Multicast | ZTE, Sanechips |
| R2-2201415 | Discussion on HFN initialization of NR MBS | ZTE, Sanechips |
| R2-2201583 | Discussion on MAC open issues for NR MBS | LG Electronics Inc. |
| R2-2201584 | Discussion on PDCP open issues for NR MBS | LG Electronics Inc. |
| R2-2201638 | PDCP status report triggering for MBS mode switching | InterDigital |
| R2-2201670 | Consideration on UP Remaining Issues of MBS | CATT |
| R2-2201812 | [Draft] LS on MBS SPS | RAN2 |
| R2-2201833 | Report of [AT116bis-e][027][MBS] PDCP and RLC initial variables | Xiaomi Communications |
| R2-2201866 | [AT116bis-e][028][MBS] MAC Open Issues (OPPO) | OPPO |
| R2-2201874 | Report of [AT116bis-e][027][MBS] PDCP and RLC initial variables (xiaomi) | Xiaomi Communications |
| R2-2201943 | [AT116bis-e][028][MBS] MAC Open Issues (OPPO) | OPPO |
| R2-2201944 | [Draft] LS on MBS SPS | RAN2 |
| R2-2202016 | LS on MBS SPS | RAN2 |
| 8.2.1 | Organizational, Requirements and Scope | |
| R2-2200276 | Draft 331 CR for DCCA UE capabilities | Intel Corporation |
| R2-2200277 | Draft 306 CR for DCCA UE capabilities | Intel Corporation |
| R2-2201089 | Introduction of SCG deactivation | Huawei, HiSilicon |
| R2-2201090 | Introduction of SCG deactivation | Huawei, HiSilicon |
| R2-2201091 | Open issues for MR DC/CA further enhancements | Huawei, HiSilicon |
| R2-2201397 | [Post116-e][213][R17 DCCA] Running MAC CR for SCG deactivation (vivo) | vivo |
| R2-2201561 | Running 37.340 CR for SCG deactivation | ZTE Corporation |
| R2-2201646 | Introduction of CPA and inter-SN CPC | CATT |
| R2-2201647 | Introduction of CPA and inter-SN CPC | CATT |
| R2-2201648 | Introduction of CPA and inter-SN CPC | CATT |
| R2-2201816 | Introduction of CPA and inter-SN CPC | CATT |
| R2-2201817 | Introduction of CPA and inter-SN CPC | CATT |
| R2-2201818 | Introduction of CPA and inter-SN CPC | CATT |
| R2-2201998 | Running CR to 38.321 for SCG activation/deactivation | vivo |
| R2-2202027 | Introduction of efficient SCG activation/deactivation | Huawei, HiSilicon |
| R2-2202028 | Introduction of efficient SCG activation/deactivation | Huawei, HiSilicon |
| R2-2202029 | Open issues for MR DC/CA further enhancements | Huawei, HiSilicon |
| R2-2202032 | Running 37.340 CR for SCG deactivation | ZTE Corporation |
| 8.2.2.1 | Deactivation of SCG and UE behaviour in deactivated SCG | |
| R2-2200057 | [Post116-e][225][R17 DCCA] Remaining details for SCG deactivation | Huawei (rapporteur) |
| R2-2200308 | QoS flow remapping during SCG deactivation | Fujitsu |
| R2-2200380 | Considerations on UE measurement and reporting in deactivated SCG | KDDI Corporation |
| R2-2200387 | SCG deactivation indication when resuming from RRC_INACTIVE due to MO data | OPPO |
| R2-2200583 | DC power sharing for deactivated SCG | Samsung Electronics Polska |
| R2-2200601 | Partial MAC reset upon SCG deactivation | Samsung Electronics Polska |
| R2-2200604 | Discussion on UE behaviour when SCG is deactivated | ZTE Corporation, Sanechips |
| R2-2200647 | Remaining issues on deactivation of SCG | NTT DOCOMO INC. |
| R2-2200771 | Discussion on SCG deactivation | Lenovo, Motorola Mobility |
| R2-2200881 | Open issues in deactivation of SCG | Nokia, Nokia Shanghai Bell |
| R2-2201075 | UE behavior in deactivated SCG and SCG deactivation | Qualcomm Incorporated |
| R2-2201092 | UE requested SCG deactivation | Huawei, HiSilicon |
| R2-2201248 | Discussion on SCG Deactivation and UE Behavior | CATT |
| R2-2201295 | Further discussion on TCI State indication in RRC | MediaTek Inc. |
| R2-2201296 | CSI-RS reporting for deactivated SCG | MediaTek Inc. |
| R2-2201318 | Remaining issues for UE behaviour in deactivated SCG | SHARP Corporation |
| R2-2201319 | Remaining issues for MAC procedure in deactivated SCG | SHARP Corporation |
| R2-2201342 | Discussion on updating TCI states | NTT DOCOMO, INC. |
| R2-2201416 | Partial MAC reset upon SCG deactivation | DENSO CORPORATION |
| R2-2201563 | Deactivation of SCG and UE behaviour in deactivated SCG | Ericsson |
| R2-2201574 | UE Measurements in SCG Deactivation | LG Electronics |
| R2-2201639 | Deactivation of SCG | InterDigital |
| R2-2201640 | Measurements while the SCG is deactivated | InterDigital |
| R2-2201701 | Summary of [AT116bis-e][221][DCCA] MAC aspects (Samsung) | Samsung |
| R2-2201711 | LS on efficient activation/de-activation mechanism for one SCG | RAN2 |
| 8.2.2.2 | Activation of deactivated SCG | |
| R2-2200542 | Futher discussion on UE initiated SCG fast activation | Futurewei |
| R2-2200584 | PHR issues for SCG activation | Samsung Electronics Polska |
| R2-2200605 | Activation of deactivated SCG | ZTE Corporation, Sanechips |
| R2-2200637 | Discussion on activation of deactivated SCG | Spreadtrum Communications |
| R2-2200649 | UP details of deactivated SCG activation | Transsion Holdings |
| R2-2200772 | Discussion on SCG activation | Lenovo, Motorola Mobility |
| R2-2200882 | Open issues in activation of SCG | Nokia, Nokia Shanghai Bell |
| R2-2200895 | Remaining issues on SCG (de)activation | CMCC |
| R2-2201060 | Activation of deactivated SCG | Qualcomm Incorporated |
| R2-2201093 | UE initiated SCG activation | Huawei, HiSilicon |
| R2-2201097 | Reply LS on efficient activation/de-activation mechanism for one SCG (R2-2109368/R4-2115440) | Huawei, HiSilicon |
| R2-2201117 | On the non-essentiality of MAC CE based SCG deactivation | Apple |
| R2-2201249 | Considerations on Activation of Deactivated SCG | CATT |
| R2-2201362 | Discussion on SCG activation and deacitvation | LG Electronics Inc. |
| R2-2201393 | Activation of deactivated SCG | vivo |
| R2-2201431 | SCG/split bearer handling upon SCG deactivation and SCell state upon SCG activation | Sharp |
| R2-2201538 | Conditional reconfiguration execution while SCG is deactivated | Sharp |
| R2-2201562 | Efficient SCG activation | Ericsson |
| R2-2201592 | UP details of deactivated SCG activation | Transsion Holdings |
| R2-2201641 | Activation of SCG | InterDigital |
| R2-2201702 | Summary of [AT116bis-e][222][DCCA] Uplink aspects (Huawei) | Huawei |
| 8.2.2.3 | Other aspects of SCG activation/deactivation | |
| R2-2200388 | Fast MCG recovery based on SCG deactivation | OPPO |
| R2-2200612 | UL data arrival and MCG link recovery | NEC |
| R2-2200896 | Considerations for Fast MCG link recovery with deactivated SCG | CMCC |
| R2-2201073 | Other aspects of SCG activation/deactivation | Qualcomm Incorporated |
| R2-2201115 | Simple MCG recovery procedure using deactivated SCG for Rel-17 | Apple |
| R2-2201116 | CR TP for MCG recovery procedure using deactivated SCG for Rel-17 | Apple |
| R2-2201317 | Deactivation of SCG | LG Electronics Finland |
| R2-2201333 | Discussion on SCG (de)activation | NTT DOCOMO, INC. |
| R2-2201394 | Fast MCG recovery via deactivated SCG | vivo |
| R2-2201432 | Fast MCG link recovery via deactevated SCG | Sharp |
| R2-2201575 | Rest issues of SCG Activation | LG Electronics |
| R2-2201703 | Summary of [AT116bis-e][223][DCCA] MCG failure recovery (Apple) | Apple |
| 8.2.3.1 | CPAC procedures from network perspective | |
| R2-2200361 | Discussion on the CG-CandidateList | Google Inc. |
| R2-2200362 | Support modification and cancellation of C-PSCells in the CG-CandidateList | Google Inc. |
| R2-2200589 | Discussion on CPAC procedures from NW perspective | vivo |
| R2-2200613 | Skip response from S-SN in SN-initiated CPC | NEC |
| R2-2200773 | Discussion on CPAC from NW perspective | Lenovo, Motorola Mobility |
| R2-2200923 | Remaining issues on CPAC procedure | ZTE Corporation, Sanechips |
| R2-2200924 | Further consideration on CPAC procedure | ZTE Corporation, Sanechips |
| R2-2201000 | CPAC network procedures | Ericsson |
| R2-2201072 | CPAC procedures from network perspective | Qualcomm Incorporated |
| R2-2201081 | Solving open issues for Rel-17 CPAC | Nokia, Nokia Shanghai Bell |
| R2-2201082 | Clarifications to the issues found in CPAC running CRs | Nokia, Nokia Shanghai Bell |
| R2-2201250 | Discussion on CPAC from NW perspective | CATT |
| R2-2201305 | CPAC procedure for SCG update | Samsung R&D Institute UK |
| R2-2201704 | Report of [AT116bis-e][224][DCCA] CPAC procedures from NW perspective (CATT) | CATT |
| R2-2201712 | LS to RAN3 on CPAC | RAN2 |
| 8.2.3.2 | CPAC procedures from UE perspective | |
| R2-2201001 | UE procedures and signalling for CPAC | Ericsson |
| R2-2201094 | UE behaviour upon CPAC execution | Huawei, HiSilicon |
| R2-2201112 | Text proposal to CPAC RRC running CR | Apple |
| R2-2201251 | Remaining issues on CPAC from UE perspective | CATT |
| 8.2.3.3 | Other CPAC aspects | |
| R2-2200341 | CPC-based SCG RLF handling | ITRI |
| R2-2200590 | Discussion on other aspects for CPAC | vivo |
| R2-2200614 | Further discussion on Co-existence of CHO and CPAC | NEC |
| R2-2200615 | CPA with SN-terminated MCG bearer configuration | NEC |
| R2-2200774 | Miscellaneous issues on CPAC | Lenovo, Motorola Mobility |
| R2-2200897 | Combination of CPAC and CHO | CMCC |
| R2-2200925 | Discussion on coexistence of CHO and CPAC | ZTE Corporation, Sanechips |
| R2-2201074 | Other CPAC aspects | Qualcomm Incorporated |
| R2-2201210 | Other issues on CPAC | LG Electronics |
| R2-2201252 | Discussion on CPAC Failure Handling and CPAC Co-existence with CHO | CATT |
| R2-2201477 | Discussion on CPAC failure handling | NTT DOCOMO INC. |
| R2-2201642 | SCG failure recovery with CPAC | InterDigital |
| R2-2201643 | Coexistence of CHO and CPC | InterDigital, Nokia, Nokia Shanghai Bell |
| 8.2.4 | Temporary RS for SCell activation | |
| R2-2200096 | LS on triggering signalling of temporary RS for SCell activation (R1-2112983; contact: Huawei) | RAN1 |
| R2-2200389 | Discussion on TRS activation for fast SCell activation | OPPO |
| R2-2200390 | Introduction of TRS based SCell activation-38321 | OPPO |
| R2-2200391 | Introduction of TRS based SCell activation-38331 | OPPO |
| R2-2200543 | Discussion on TRS for fast SCell activation Alt1 vs Alt2 | Futurewei |
| R2-2200582 | Leftover issues for TRS based SCell activation | Samsung Electronics Polska |
| R2-2200883 | Temporary RS activation | Nokia, Nokia Shanghai Bell |
| R2-2201041 | temporary RS for SCell activation | Ericsson |
| R2-2201095 | MAC CE and RRC signalling for efficient SCell activation | Huawei, HiSilicon, Samsung, vivo, LG Electronics |
| R2-2201395 | Discussion on Temporary RS activation for fast SCell activation | vivo |
| R2-2201713 | Introduction of TRS based SCell activation | OPPO |
| R2-2201714 | Introduction of TRS based SCell activation-38331 | OPPO |
| R2-2201715 | LS on RAN2 agreements for TRS-based Scell activation | RAN2 |
| R2-2202056 | LS on RAN2 agreements for TRS-based Scell activation | RAN2 |
| 8.2.5 | UE capabilities | |
| R2-2200275 | Discussion on remaining issues on DCCA UE capabilities | Intel Corporation |
| R2-2201096 | UE capabilities | Huawei, HiSilicon |
| R2-2201297 | Discussion on CPAC Capabilities | MediaTek Inc. |
| R2-2202030 | Draft 331 CR for DCCA UE capabilities | Intel Corporation |
| R2-2202031 | Draft 306 CR for DCCA UE capabilities | Intel Corporation |
| 8.3.1 | Organizational, Requirements and Scope | |
| R2-2200132 | Reply LS on gap handling for MUSIM (R4-2120342; contact: vivo) | RAN4 |
| R2-2200144 | LS on Paging Cause Indication for Voice Service Supported in RRC Inactive assistance information (S2-2109303; contact: Sony) | SA2 |
| R2-2200652 | Running LTE RRC CR for MUSIM | Samsung Electronics Co., Ltd |
| R2-2200800 | Running NR RRC CR for MUSIM | vivo |
| R2-2200801 | Remianing issue list | vivo |
| R2-2201485 | Running CR to 38300 for Multi-USIM devices support | Ericsson |
| R2-2201486 | Running CR to 36300 for Multi-USIM devices support | Ericsson |
| R2-2201490 | Discussion on the remaining FFS in TS 36.300 and 38.300 | Ericsson, Samsung |
| R2-2201697 | Running CR to 36.304 for Multi-USIM devices | China Telecom |
| R2-2201972 | Running CR to 36300 for Multi-USIM devices support | Ericsson |
| R2-2201973 | Running CR to 38300 for Multi-USIM devices support | Ericsson |
| R2-2201979 | Running LTE RRC CR for MUSIM | Samsung Electronics Co., Ltd |
| R2-2201997 | Running NR RRC CR for MUSIM | vivo |
| R2-2201999 | [Post116bis-e][202][MUSIM] Open issues for MUSIM | vivo |
| 8.3.2 | Paging collision avoidance | |
| R2-2200414 | SI Change | Lenovo, Motorola Mobility |
| R2-2200470 | Remaining issues on 36.304 running CR | China Telecommunications, Samsung |
| R2-2200571 | Alternative IMSI calculation for paging collision avoidance | NEC |
| R2-2200802 | Remaining issue for EPS Paging Collision avoidance | vivo |
| R2-2201705 | Summary of [AT116bis-e][230][MUSIM] Paging collision handling (China Telecom) | China Telecom |
| R2-2201718 | LS to SA2 and CT1 on alternative IMSI for MUSIM | RAN2 |
| 8.3.3 | UE notification on network switching for multi-SIM | |
| R2-2200211 | Remaining issues on network switching for MUSIM | Samsung Electronics Co., Ltd |
| R2-2200230 | Remaining Details for Periodic and Aperiodic Gaps | OPPO |
| R2-2200231 | Remaining Details on MUSIM Assistance Information for Leaving Case | OPPO |
| R2-2200359 | Remaining open issues on network switching for MUSIM | Intel Corporation |
| R2-2200489 | Configuration of MUSIM Gaps | Qualcomm Incorporated |
| R2-2200490 | Further details of network switching for Multi-SIM | Qualcomm Incorporated |
| R2-2200522 | Remaining issues of Network switching for MUSIM | China Telecom |
| R2-2200572 | Remaining issues on scheduling gap for network switching | NEC |
| R2-2200631 | UE indication on switching | Spreadtrum Communications |
| R2-2200632 | Busy indication transmission | Spreadtrum Communications |
| R2-2200671 | On remaining issues for MUSIM Gap configuration | Nokia, Nokia Shanghai Bells |
| R2-2200672 | On remaining issues for switching notification for leaving RRC connection | Nokia, Nokia Shanghai Bells |
| R2-2200736 | Interaction between NAS and AS for network switching | ASUSTeK |
| R2-2200737 | Configured time for network switching | ASUSTeK |
| R2-2200754 | Remaining issues for switching notification and busy indication | Lenovo, Motorola Mobility |
| R2-2200803 | Remaining open issues on MUSIM Switching | vivo |
| R2-2200904 | Remaining issues for NW switching with leaving RRC_CONNECTED | Huawei, HiSilicon |
| R2-2200920 | Remaining issues for NW switching without leaving RRC_CONNECTED | Huawei, HiSilicon |
| R2-2200950 | Discussion on RAN4 Reply LS on MUSIM gaps | Samsung R&D Institute India |
| R2-2201201 | MUSIM Signaling aspects for Scheduling gap handling | Apple |
| R2-2201215 | Release of MUSIM Gap | Sharp |
| R2-2201216 | RRC Connection release request procedure for MUSIM and power saving | Sharp |
| R2-2201228 | Remain issues for network switching with leaving RRC_CONNECTED | SHARP Corporation |
| R2-2201233 | Further Consideration on the Scheduling Gap | ZTE Corporation, Sanechips |
| R2-2201234 | Consideration on the Switching with Leaving Connected State | ZTE Corporation, Sanechips |
| R2-2201315 | Signalling design on busy indication procedure | DENSO CORPORATION |
| R2-2201316 | Further details on network switching notification | MediaTek Inc. |
| R2-2201369 | Remaining issues for MUSIM gap configuration | LG Electronics France |
| R2-2201481 | Remaining Issues for MUSIM Network Switching | Charter Communications, Inc |
| R2-2201482 | Discussion on switchover procedure without leaving RRC_CONNECTED state | Ericsson |
| R2-2201483 | Discussion on switchover procedure for leaving RRC_CONNECTED state | Ericsson |
| R2-2201576 | Paging filtering when AS-based leaving | LG Electronics |
| R2-2201577 | Considerations on Busy Indication | LG Electronics |
| R2-2201633 | Measurement Gaps Open issues | Rakuten Mobile, Inc |
| R2-2201706 | Summary of [AT116bis-e][231][MUSIM] MUSIM gap details (vivo) | vivo |
| R2-2201707 | Summary of [AT116bis-e][232][MUSIM] MUSIM configured time for leaving RRC connection (MediaTek) | MediaTek |
| R2-2201717 | LS to RAN4 on RAN2 agreement for MUSIM gaps | RAN2 |
| 8.3.5 | UE capabilities and other aspects | |
| R2-2200210 | UE capabilities and other essential aspects for MUSIM | Samsung Electronics Co., Ltd |
| R2-2200232 | UE Capabilities for MUSIM | OPPO |
| R2-2200360 | Remaining issues on UE and network capabilities for MUSIM | Intel Corporation |
| R2-2200695 | UE capability for MUSIM gaps | Qualcomm Incorporated |
| R2-2200804 | Multi-USIM related UE capabilities | vivo |
| R2-2200838 | Further discussion on UE capabilities for MUSIM operation | Nokia Italy |
| R2-2200921 | Discussion on UE capability for MUSIM | Huawei, HiSilicon |
| R2-2201202 | MUSIM UE capability aspects | Apple |
| R2-2201203 | Additional issues related to MUSIM - Aspects of MUSIM RRC Band Conflict, Processing Delay and Caller ID retrieval requirements | Apple |
| R2-2201235 | Consideration on the UE Capability for the MUSIM | ZTE Corporation, Sanechips |
| R2-2201484 | UE capabilities for Multi-USIM | Ericsson |
| R2-2202008 | Running CR to 38822 for MUSIM UE Capabilities | Huawei, HiSilicon |
| R2-2202009 | Running CR to 38331 for MUSIM UE Capabilities | Huawei, HiSilicon |
| R2-2202010 | Running CR to 38306 for MUSIM UE Capabilities | Huawei, HiSilicon |
| 8.4.1 | Organizational | |
| R2-2200008 | Remaining open issues for eIAB | Qualcomm (WI Rapporteur) |
| R2-2200023 | Remaining open issues for eIAB | Qualcomm (WI Rapporteur) |
| R2-2200065 | Reply LS on Inter-donor migration (R1-2108529; contact: Huawei) | RAN1 |
| R2-2200094 | LS on range of power control parameters for eIAB (R1-2112973; contact: Qualcomm) | RAN1 |
| R2-2200100 | LS on BAP- and RRC-related agreements from RAN3#113-e (R3-214476; contact: Ericsson) | RAN3 |
| R2-2200115 | Reply LS on inter-donor migration (R4-2115354; contact: ZTE) | RAN4 |
| R2-2200194 | Updated Rel-17 IAB Workplan | Qualcomm Incorporated, Samsung (WI rapporteurs) |
| R2-2200805 | Running CR to 37.340 for eIAB | vivo |
| R2-2201303 | Running CR of TS 38.340 for eIAB Option1 | Huawei, HiSilicon |
| R2-2201304 | Running CR of TS 38.340 for eIAB Option2 | Huawei, HiSilicon |
| R2-2201527 | Running CR to 38.321 on Integrated Access and Backhaul for NR Rel-17 | Samsung Electronics GmbH |
| R2-2201613 | Running CR to 38.331 on NR IAB enhancements | Ericsson |
| R2-2201819 | Running CR of TS 38.340 for eIAB | Huawei, HiSilicon |
| R2-2201850 | Running CR to 38.321 on Integrated Access and Backhaul for NR Rel-17 | Samsung Electronics GmbH |
| R2-2201984 | Running CR to 38.321 on Integrated Access and Backhaul for NR Rel-17 | Samsung Electronics GmbH |
| R2-2201993 | Running CR to 38.331 on NR IAB enhancements | Ericsson |
| R2-2202050 | [Post116bis-e][079][eIAB] Open Issues (Qualcomm) | Qualcomm (Rapporteur) |
| 8.4.2.1 | RLF indication | |
| R2-2200196 | Open isuses on IAB RLF indications | Qualcomm Incorporated |
| R2-2200323 | Discussion on RLF Indications | CATT |
| R2-2200351 | Open issues on IAB-node RLF indication | Intel Corporation |
| R2-2200405 | Discussion on left issue of Type-2/3 RLF indication | NEC |
| R2-2200562 | Control plane behavior at receiving BH RLF detection indication | Fujitsu |
| R2-2200563 | A mechanism to avoid a storm of BH RLF indication | Fujitsu |
| R2-2200564 | RLF indication and flow control feedback from boundary node | Fujitsu |
| R2-2200806 | Remaining Issues of BH RLF | vivo |
| R2-2200837 | Discussion on RLF indication enhancements | CANON Research Centre France |
| R2-2201051 | RLF indications and re-routingenhancements | Nokia, Nokia Shanghai Bell |
| R2-2201242 | Remaining issues of BH RLF Indications for eIAB | Kyocera |
| R2-2201301 | RLF indication and local re-routing based on flow control | Huawei, HiSilicon |
| R2-2201306 | RLF indication related issues | Samsung R&D Institute UK |
| R2-2201349 | Remaining issues on RLF indication | ZTE, Sanechips |
| R2-2201388 | Open Issues for RLF indications for dual-connected IAB nodes | Futurewei Technologies |
| R2-2201468 | Resolving open issues on BH RLF indications | LG Electronics |
| R2-2201607 | On Local Routing and Type 2/3 RLF Handling | Ericsson |
| R2-2201644 | On BH RLF indications in IAB | InterDigital |
| R2-2201692 | Summary of AI 8.4.2.1 (BH RLF indication) | LG Electronics Inc. |
| R2-2201937 | Summary of [AT116bis-e][048][eIAB] RLF indication (LG) | LG Electronics Inc. |
| 8.4.2.2 | CP-UP separation | |
| R2-2200324 | Leftovers of CP-UP Separation | CATT |
| R2-2200565 | Remaining issues on CP-UP separation | Fujitsu |
| R2-2200807 | Remainings issues on CP-UP separation | vivo |
| R2-2201053 | IAB CP-UP separation remaining issues | Nokia, Nokia Shanghai Bell |
| R2-2201302 | F1 over NR access link | Huawei, HiSilicon |
| R2-2201308 | CP-UP separation and other topology adaptation issues | Samsung R&D Institute UK |
| R2-2201350 | Discussion on CP/UP spearation | ZTE, Sanechips |
| R2-2201428 | Remaining issues on CP-UP separation | LG Electronics Inc. |
| R2-2201608 | Remaining Issues Related to CP/UP Separation in IAB Network | Ericsson |
| R2-2201651 | IAB CP-UP separation remaining issues | Nokia, Nokia Shanghai Bell |
| R2-2201679 | [Pre116bis][002][eIAB] Summary of 8.4.2.2 CP-UP separation_v00 | Ericsson |
| R2-2201992 | [Post116bis-e][076][eIAB] 38331 (Ericsson) | Ericsson |
| 8.4.2.3 | BAP routing | |
| R2-2200195 | Open issues on BAP routing | Qualcomm Incorporated |
| R2-2200325 | On BAP Routing and Rerouting | CATT |
| R2-2200352 | Open issues on BAP routing for inter-donor topology routing | Intel Corporation |
| R2-2200566 | Discussion on the routing issues | Fujitsu |
| R2-2200760 | Discussion on remaining issues for IAB rerouting | Lenovo, Motorola Mobility |
| R2-2200808 | Remaining Issues of Intra/Inter-Topology Routing | vivo |
| R2-2200842 | Discussion on the configuration of a boundary node | CANON Research Centre France |
| R2-2200907 | Introduce cost factor in local re-routing | Sony |
| R2-2200918 | BAP Header Rewriting Configuration | Sony |
| R2-2201052 | IAB inter-CU (re)routing issues | Nokia, Nokia Shanghai Bell |
| R2-2201243 | Details of routing and re-routing enhancements for eIAB | Kyocera |
| R2-2201299 | Leftover issues for BAP header rewriting based (re)routing | Huawei, HiSilicon |
| R2-2201322 | Discussion on the inter-CU routing | Samsung Electronics France SA |
| R2-2201351 | Discussion o BAP routing and rerouting | ZTE, Sanechips |
| R2-2201429 | Open issues for BAP routing operation | LG Electronics Inc. |
| R2-2201430 | Text Proposal of TS 38.340 for BAP routing operation | LG Electronics Inc. |
| R2-2201606 | Boundary IAB node behaviour for partial inter-donor migration | Ericsson |
| R2-2201669 | [Pre116bis][003][eIAB] Summary of 8.4.2.3 BAP routing (Qualcomm) | Qualcomm |
| R2-2201690 | [Pre116bis][003][eIAB] Summary of 8.4.2.3 BAP routing (Qualcomm) | Qualcomm |
| R2-2201820 | TS 38.340 related open issue for eIAB | Huawei, HiSilicon |
| R2-2201879 | [AT116bis-e][049][eIAB] BAP Routing | Qualcomm Inc |
| R2-2202025 | Updated MBS open issue list | Huawei, HiSilicon |
| 8.4.2.4 | Other | |
| R2-2200353 | intra-donor CU service interruption reduction | Intel Corporation |
| R2-2200809 | On Congestion Triggered Local Re-routing | vivo |
| R2-2200810 | Discussion on LCP Extension | vivo |
| R2-2201054 | PDCP aspects of a migrating node withholding a child node’s RRC reconfiguration | Nokia, Nokia Shanghai Bell |
| R2-2201298 | LCG extension and R1 related MAC CE design | Huawei, HiSilicon |
| R2-2201323 | Discussion on congestion mitigation in Rel-17 eIAB | Samsung Electronics France SA |
| R2-2201353 | Discussion on MAC CEs for PHY layer support | ZTE, Sanechips |
| R2-2201427 | Remaining issues on LCG extension | LG Electronics Inc. |
| R2-2201526 | Extended BSR and padding | Samsung Electronics GmbH |
| R2-2201610 | RAN2 impact of miscellaneous features driven by RAN3 and RAN1 | Ericsson |
| R2-2201645 | CHO in IAB | InterDigital |
| R2-2201876 | Summary of discussion [AT116bis-e][050][eIAB] MAC (Samsung) | Samsung (rapporteur) |
| R2-2201985 | Summary of discussion [Post116bis-e][077][eIAB] 38321 (Samsung) | Samsung (rapporteur) |
| 8.4.3 | UE capabilities | |
| R2-2200354 | UE capabilities for Rel-17 eIAB | Intel Corporation |
| R2-2200355 | UE capabilities for Rel-17 eIAB | Intel Corporation |
| R2-2201055 | IAB UE feature list | Nokia, Nokia Shanghai Bell |
| R2-2201300 | UE capability issues for eIAB | Huawei, HiSilicon |
| R2-2201352 | Discussion on R17 IAB-MT capabilities | ZTE, Sanechips |
| R2-2201609 | On eIAB capabilities | Ericsson |
| R2-2201689 | Summary of 8.4.3 UE caps | Intel Corporation (Rapporteur) |
| R2-2201912 | Summary of discussion [AT116bis-e][051][eIAB] UE Caps (Intel) | Intel Corporation (Rapporteur) |
| 8.5.1 | Organizational | |
| R2-2200024 | MAC Running CR for Rel-17 IIoT/URLLC | Samsung |
| R2-2200052 | Stage-2 Running CR for Rel-17 IIoT/URLLC | Nokia, Nokia Shanghai Bell |
| R2-2200080 | LS on propagation delay compensation (R1-2112834; contact: Huawei) | RAN1 |
| R2-2200951 | RRC running CR for IIoT | Ericsson |
| R2-2200992 | UE capabilities for Rel-17 IIoT / URLLC | Intel Corporation |
| R2-2201131 | RAN1 feature impact on MAC in Rel-17 IIoT/URLLC | Apple |
| R2-2201132 | Text proposals to MAC running CR for Rel-17 IIoT/URLLC | Apple |
| R2-2201373 | MAC impact of RAN1 Rel-17 HARQ deferral | Xiaomi Communications |
| R2-2201990 | MAC Running CR for Rel-17 IIoT/URLLC | Samsung |
| R2-2202003 | Stage-2 Running CR for Rel-17 IIoT/URLLC | Nokia, Nokia Shanghai Bell |
| R2-2202006 | Open issues in CP for IIoT | Ericsson |
| R2-2202007 | RRC running CR for IIoT | Ericsson |
| R2-2202020 | Open issues in UP for IIoT | Samsung |
| 8.5.2 | Enhancements for support of time synchronization | |
| R2-2200060 | RE: LS on Time Synchronization | IEEE 1588 WG |
| R2-2200182 | Signalling for Support of Propagation Delay Compensation | Nokia, Nokia Shanghai Bell |
| R2-2200320 | RTT-based PDC and TA-based PDC | CATT |
| R2-2200477 | Discussion about propagation delay compensation for accurate time synchronization | Huawei, HiSilicon |
| R2-2200611 | Discussion on propagation delay compensation for TSN | NTT DOCOMO INC. |
| R2-2200678 | Discussion on RTT-based PDC | ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd |
| R2-2200761 | Signaling procedure of RTT based propagation delay compensation | Lenovo, Motorola Mobility |
| R2-2200872 | Discussion on RTT-based PDC Enhancement | CMCC |
| R2-2200926 | Remaining issues on time synchronization enhancement | OPPO |
| R2-2200952 | Propagation delay compensation enhancements | Ericsson |
| R2-2200991 | Remaining issues of timing synchronization | Intel Corporation |
| R2-2201016 | Propagation Delay Compensation for TSN | Qualcomm Incorporated |
| R2-2201263 | Discussion on propagation delay compensation | vivo |
| R2-2201367 | Issues on PDC | Samsung |
| R2-2201826 | Report of [AT116bis-e][503][IIoT] Tsynch open issues (ZTE) | ZTE (email discussion rapporteur) |
| R2-2201976 | LS on PDC for Time Synchronization | RAN2 |
| 8.5.3 | Uplink enhancements for URLLC in unlicensed controlled environments | |
| R2-2200183 | Remaining Issues on Configured Grant for URLLC in Unlicensed | Nokia, Nokia Shanghai Bell |
| R2-2200321 | Leftovers of UCE | CATT |
| R2-2200478 | Remaining issues about uplink enhancements for URLLC in UCE | Huawei, HiSilicon |
| R2-2200927 | Remaining issues on URLLC over NRU | OPPO |
| R2-2200953 | Remaining issues in UL CG enhancements | Ericsson |
| R2-2201018 | CG Harmonization for Unlicensed Controlled Environment | Qualcomm Incorporated |
| R2-2201226 | Further Consideration on the Intra-UE multiplexing in UCE | ZTE Corporation,Sanechips |
| R2-2201264 | Remaining Issues for UCE | vivo |
| R2-2201285 | Remaining issues for IIoT in UCE | III |
| R2-2201368 | Remaining Issues on CG Enhancement and Intra-UE Prioritization | Samsung |
| R2-2201374 | UE processing time restriction on the retransmission grant selection | Xiaomi Communications |
| R2-2201460 | Remaining issues for UCE | MediaTek Inc. |
| R2-2201827 | Report of [AT116bis-e][504][IIOT] UCE open issues | vivo (Rapporteur) |
| R2-2201922 | Report of [AT116bis-e][504][IIOT] UCE open issues | vivo (Rapporteur) |
| 8.5.4 | RAN enhancements based on new QoS | |
| R2-2200003 | Report of [Post116-e][513][IIoT] QoS Survival Time (Apple) | Apple |
| R2-2200184 | Some open issues for Survival Time Support | Nokia, Nokia Shanghai Bell |
| R2-2200309 | Analysis on HARQ-NACK solution | Fujitsu |
| R2-2200310 | Survival Time Mode and Measurement Gap | Fujitsu |
| R2-2200311 | L1/L2 configuration adaptation | Fujitsu |
| R2-2200322 | HARQ NACK solution: leftover issues and TP | CATT |
| R2-2200369 | Additional aspects on resource in Survival Time | III |
| R2-2200479 | Discussion about UE behaviors for Survival Time state operation | Huawei, HiSilicon |
| R2-2200704 | N and combined Tx-side timer for IIoT QoS | ZTE, Sanechips, China Southern Power Grid Co., Ltd, TCL Communication Ltd., vivo |
| R2-2200708 | Remaining issues on the support of survival time | Lenovo, Motorola Mobility |
| R2-2200873 | Remaining Issues on HARQ-NACK Solution | CMCC |
| R2-2200928 | Remaining issues on survival time | OPPO |
| R2-2200954 | Remaining details on survival time enhancement | Ericsson |
| R2-2200990 | Survival time handling | Intel Corporation |
| R2-2201019 | RAN Enhancement to support Survival Time | Qualcomm Incorporated |
| R2-2201133 | Remaining QoS solution aspects | Apple |
| R2-2201173 | Remaining issues on the support of survival time | InterDigital |
| R2-2201265 | Discussion on HARQ NACK solution | vivo |
| R2-2201375 | Remaining issues of survival time requirements | Xiaomi Communications |
| R2-2201520 | CG status and PDCP Duplication status | LG Electronics |
| R2-2201521 | Remaining issues on QoS support | LG Electronics |
| R2-2201522 | Selective RLC activation for PDCP duplication in ST state | LG Electronics |
| R2-2201530 | Finalising Survival Time related enhancements | Samsung Electronics GmbH |
| R2-2201622 | Considerations on UE Survival Time support | Sequans Communications |
| 8.6.1 | Organizational | |
| R2-2200025 | Introduction of SDT | Nokia, Nokia Shanghai Bell |
| R2-2200031 | Running MAC CR for small data | Huawei, HiSilicon |
| R2-2200032 | Summary of [Post116-e][507][SDT] MAC running CR update (Huawei) | Huawei, HiSilicon |
| R2-2200050 | RRC Running CR for SDT | ZTE Corporation (rapporteur) |
| R2-2200073 | Reply LS on the physical layer aspects of small data transmission (R1-2112782; contact: ZTE) | RAN1 |
| R2-2200502 | UE capabilities for Rel-17 SDT WI | Intel Corporation |
| R2-2200503 | UE capabilities for Rel-17 SDT WI | Intel Corporation |
| R2-2200504 | UE capabilities for Rel-17 SDT WI | Intel Corporation |
| R2-2201027 | Updated RRC running CR for SDT | ZTE corporation (rapporteur) |
| R2-2201357 | Discussion on MAC running CR | LG Electronics Inc. |
| R2-2201828 | Reply LS on the L1 aspects of small data transmission | RAN2 |
| R2-2201877 | LS on resume cause | RAN2 |
| R2-2202014 | Stage-2 running CR Introduction of SDT | Nokia, Nokia Shanghai Bell |
| R2-2202021 | Updated RRC running CR for SDT | ZTE corporation (rapporteur) |
| R2-2202022 | CP open issues list for SDT (email: [POST116bis-e][511]) | ZTE corporation (rapporteur) |
| R2-2202041 | Running MAC CR for Small Data Transmission | Huawei, HiSilicon |
| R2-2202042 | Summary of [POST116bis-e][510][Sdata] Running MAC CR | Huawei, HiSilicon |
| 8.6.2 | User plane common aspects | |
| R2-2200203 | User Plane Aspects of RACH and CG based SDT | Samsung Electronics Co., Ltd |
| R2-2200336 | Consideration on UP remaining issues | CATT |
| R2-2200435 | Remaining issues of user plane common aspects | Huawei, HiSilicon |
| R2-2200573 | Remaining user plane aspects of SDT | NEC |
| R2-2200643 | Discussion on user plane issues of SDT | OPPO |
| R2-2200726 | Remaining issues on UP aspects of SDT | Qualcomm Incorporated |
| R2-2200863 | Data volume calculation for SDT | CMCC |
| R2-2200985 | Common aspects for SDT | Ericsson |
| R2-2201024 | Remaining UP issues for SDT | InterDigital |
| R2-2201028 | User plane common aspects of SDT | ZTE corporation, Sanechips |
| R2-2201124 | User plane aspects of SDT | Apple |
| R2-2201321 | Remaining UP issues in SDT | LG Electronics Inc. |
| R2-2201439 | Remaining Issues on Subsequent UL transmission during SDT | vivo |
| R2-2201570 | Consideration on UP remaining issues | CATT |
| R2-2201586 | UP aspects for SDT | Nokia, Nokia Shanghai Bell |
| R2-2201825 | UP open issues – outcome of email discussion 501 | LG electronics |
| R2-2201867 | [AT116bis-e][501][SData] Summary of UP SDT open issues | LG Electronics Inc. |
| R2-2202040 | [POST116bis-e][510][Sdata] UP open issues (Huawei) | Huawei, HiSilicon |
| 8.6.3 | Control plane common aspects | |
| R2-2200026 | Report of [Post116-e][510][SDT] CCCH and DCCH (Nokia) | Nokia, Nokia Shanghai Bell |
| R2-2200201 | Paging Monitoring during SDT procedure | Samsung Electronics Co., Ltd |
| R2-2200202 | RNA update and SI request handling during SDT procedure | Samsung Electronics Co., Ltd |
| R2-2200312 | Handling of SDTF detection timer | Fujitsu |
| R2-2200313 | RAN paging reception and response during SDT | Fujitsu |
| R2-2200337 | Consideration on some CP issues | CATT |
| R2-2200505 | Control Plane leftover issues on SDT procedure | Intel Corporation |
| R2-2200574 | Remaining control plane aspects of SDT | NEC |
| R2-2200644 | Discussion on control plane issues of SDT | OPPO |
| R2-2200663 | Emergency call in the middle of SDT operation | InterDigital, Europe, Ltd. Rakuten Mobile Inc. |
| R2-2200696 | Handling of SDT failure timer | InterDigital, Europe, Ltd. |
| R2-2200727 | Remaining issues on CP aspects of SDT | Qualcomm Incorporated |
| R2-2200811 | Control plane common aspects for SDT | Huawei, HiSilicon |
| R2-2200919 | Subsequent SDT failure detection timer | Sony |
| R2-2200986 | CP aspects for SDT | Ericsson |
| R2-2201029 | CP open issues for SDT | ZTE corporation, Sanechips |
| R2-2201125 | Control plane aspects of SDT | Apple |
| R2-2201126 | Power Saving for SDT | Apple |
| R2-2201174 | DCCH-based indication of non-SDT data arrival | Intel Corporation, ZTE Corporation, Sanechips, Samsung, Xiaomi, MediaTek, Radisys and Reliance JIO, Qualcomm, CMCC, OPPO, Lenovo, Sony, Apple |
| R2-2201217 | RNA Update during SDT | Sharp |
| R2-2201358 | Remaining issues on Control Plane Aspects for SDT | LG Electronics Inc. |
| R2-2201376 | Clarification on the area configured for ROHC continuity | Xiaomi Communications |
| R2-2201377 | Paging reception during SDT | Xiaomi Communications |
| R2-2201378 | RACH failure in subsequent data transmission phase | Xiaomi Communications |
| R2-2201440 | Remaining Issues on RRC-Controlled SDT procedure | vivo |
| R2-2201441 | Further Consideration on the Handling of non-SDT Data Arrival | vivo |
| R2-2201495 | SDT control plane aspects | Nokia, Nokia Shanghai Bell |
| R2-2201496 | RRC procedure for SDT | Nokia, Nokia Shanghai Bell |
| R2-2201535 | Remaining issues for non-SDT data arrival | China Telecommunications |
| R2-2201571 | Consideration on some CP issues | CATT |
| R2-2201674 | Summary of Rel-17 SDT contributions on Control Plane Common Aspects | InterDigital |
| R2-2201821 | [DRAFT] LS on Security for Small Data Transmission | Nokia |
| R2-2201822 | LS on resume cause | RAN2 |
| R2-2201823 | [draft] LS on RAN3 impacts for CCCH based solution for non-SDT handling | Intel Corporation |
| R2-2201824 | Summary of Rel-17 SDT contributions on Control Plane Common Aspects | Interdigital |
| R2-2201868 | Summary of Rel-17 SDT contributions on Control Plane Common Aspects | Interdigital |
| R2-2201920 | [DRAFT] LS on Security for Small Data Transmission | Nokia |
| R2-2201930 | [draft] LS on RAN3 impacts for CCCH based solution for non-SDT handling | Intel Corporation |
| R2-2201955 | [DRAFT] LS on Security for Small Data Transmission | Nokia |
| R2-2201977 | LS on RAN3 impacts for non-SDT handling | RAN2 |
| R2-2201983 | LS on Security for Small Data Transmission | RAN2 |
| 8.6.4 | Aspects specific to RACH based schemes | |
| R2-2200338 | Anchor relocation during SDT | CATT |
| R2-2200506 | RACH leftover issues on RA-SDT procedure | Intel Corporation |
| R2-2200638 | Discussion on RACH-based SDT | Spreadtrum Communications |
| R2-2200645 | Discussion on swiching from RA-SDT to non-SDT | OPPO |
| R2-2200729 | Remaining issues on RACH based SDT | Qualcomm Incorporated |
| R2-2200738 | Discussion on triggering legacy RA for RA-SDT | ASUSTeK |
| R2-2200779 | Analysis on open issue of RA based SDT | Lenovo, Motorola Mobility |
| R2-2200983 | RACH based small data transmission | Ericsson |
| R2-2201355 | Switching cases of SDT and non-SDT | LG Electronics Inc. |
| R2-2201356 | Discussion on Carrier selection for SDT | LG Electronics Inc. |
| R2-2201572 | Anchor relocation during SDT | CATT |
| 8.6.5 | Aspects specific to CG based schemes | |
| R2-2200033 | Summary of [Post116-e][509][SDT] CG open issues (Huawei) | Huawei, HiSilicon |
| R2-2200204 | CG-SDT-TAT expiry handing during the CG-SDT procedure | Samsung Electronics Co., Ltd |
| R2-2200339 | Consideration on CG-SDT | CATT |
| R2-2200436 | Remaining issues of CG-SDT | Huawei, HiSilicon |
| R2-2200437 | Further discussion on TA issues for CG-SDT | Huawei, HiSilicon, ZTE corporation |
| R2-2200507 | CG-SDT leftover issues | Intel Corporation |
| R2-2200646 | Discussion on open issues of CG-SDT | OPPO |
| R2-2200717 | Remaining issues on CG-based Small data transmission | Lenovo, Motorola Mobility |
| R2-2200734 | Remaining issues on CG based SDT | Qualcomm Incorporated |
| R2-2200739 | Discussion on CS-RNTI configuration for CG-SDT | ASUSTeK |
| R2-2200984 | Details of CG based SDT | Ericsson |
| R2-2201023 | Remaining issues for CG-based SDT | InterDigital |
| R2-2201030 | Aspects specific to CG-SDT | ZTE corporation, Sanechips |
| R2-2201338 | Aspects specific to CG-SDT | Nokia, Nokia Shanghai Bell |
| R2-2201379 | Clarification on the RSRP-based TA validation | Xiaomi Communications |
| R2-2201442 | Supporting Small Data Transmission via CG PUSCH | vivo |
| R2-2201537 | Remaining issues on CG based SDT | China Telecommunications |
| R2-2201573 | Consideration on CG-SDT | CATT |
| R2-2201657 | Summary of [Post116-e][509][SDT] CG open issues (Huawei) | Huawei, HiSilicon |
| 8.7.1 | Organizational | |
| R2-2200038 | Work planning for R17 SL relay | OPPO, CMCC |
| R2-2200062 | LS on the indication of discovery message and PC5-S signalling to ProSe layer (C1-217167; contact: CATT) | CT1 |
| R2-2200165 | Indication of Discovery Message and PC5-S Signalling to ProSe Layer | CATT |
| R2-2200178 | Initial consideration on UE capability of sidelink relay | Qualcomm Incorporated |
| R2-2200364 | Running CR for TS 38.351 | OPPO |
| R2-2200365 | Remaining open issues for R17 SL relay | OPPO |
| R2-2200366 | Discussion on C1-217167 | OPPO |
| R2-2200658 | Running CR of 38.322 for SL Relay | Samsung |
| R2-2200659 | Running CR of 38.323 for SL Relay | Samsung |
| R2-2200789 | Stage 2 Running CR on Introduction of R17 SL Relay | MediaTek Inc. |
| R2-2200944 | Stage 2 corrections for SL Relay | Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2200945 | RRC corrections for SL Relay | Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2201160 | Running CR of 38.304 for SL relay | Ericsson |
| R2-2201507 | RRC running CR for SL relay | Huawei, HiSilicon |
| R2-2201508 | Stage3 open issues in RRC running CR | Huawei, HiSilicon |
| R2-2201695 | Summary [AT116bis-e][606][Relay] CT1 LS on discovery (CATT) | CATT |
| R2-2201696 | LS reply on the indication of discovery message and PC5-S signalling to ProSe layer | CATT |
| R2-2201721 | Remaining Open issue list of R17 Sidelink Relay WI | OPPO |
| R2-2201725 | Stage 2 Running CR on Introduction of R17 SL Relay | MediaTek Inc. |
| R2-2201726 | Running CR of 38.322 for SL Relay | Samsung |
| R2-2201727 | Running CR of 38.323 for SL Relay | Samsung |
| R2-2201728 | Running CR of 38.304 for SL relay | Ericsson |
| R2-2201781 | LS reply on the indication of discovery message and PC5-S signalling to ProSe layer | RAN2 |
| R2-2201811 | Introduction of Rel-17 Sidelink Relay | Huawei, HiSilicon |
| R2-2201905 | Summary report of [AT116bis-e][607][Relay] Relay UE capabilities (Qualcomm) | Qualcomm Incorporated |
| R2-2201906 | Draft 38.306 CR for sidelink relay UE capabilities | Qualcomm Incorporated |
| R2-2201956 | MAC running CR for SL relay | Apple |
| R2-2201996 | Running CR for TS 38.351 | OPPO |
| 8.7.2.1 | Control plane procedures | |
| R2-2200166 | Control Plane Procedures of L2 Relay | CATT |
| R2-2200172 | Remaining issues on RRC connection management of L2 U2N relay | Qualcomm Incorporated |
| R2-2200173 | Remaining issues on paging and SIB forwarding in L2 U2N relay | Qualcomm Incorporated |
| R2-2200226 | Leftover issues of Control plane procedures for L2 U2N relaying | Intel Corporation |
| R2-2200367 | Remaining WA for R17 SL Relay | OPPO, Qualcomm Incorporated, Samsung, Intel Corporation, Apple, Huawei, HiSilicon, MediaTek Inc., Xiaomi, Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2200372 | Left Issues on Control Plane Aspects for L2 Relay | OPPO |
| R2-2200410 | Monitoring Paging by a U2N Relay | Lenovo, Motorola Mobility |
| R2-2200412 | SI acquisition by a remote UE | Lenovo, Motorola Mobility |
| R2-2200471 | Open issues on L2 Control Plane Procedures | vivo |
| R2-2200512 | Discussion on RRC reestablishment related parameters for L2 sidelink relay | China Telecom |
| R2-2200551 | Remaining issues for Control plane | MediaTek Inc. |
| R2-2200552 | RAN sharing | MediaTek Inc., CATT, OPPO, Qualcomm Incorporated, ZTE, Huawei, HiSilicon, Apple, InterDigital |
| R2-2200625 | Left issues on control plane procedures for L2 U2N relay | Spreadtrum Communications |
| R2-2200653 | Remaining issues for paging and SI delivery | Samsung |
| R2-2200740 | Discussion on sidelink RLC bearer management for L2 U2N relay | ASUSTeK |
| R2-2200741 | Discussion on missing procedural text for applying C-RNTI of Remote UE | ASUSTeK |
| R2-2200742 | Discussion on missing procedural text for Relay UE to apply SL-RLC0 configuration | ASUSTeK |
| R2-2200743 | Reflecting Stage 2 agreement on sidelink resource allocation mode for U2N relay | ASUSTeK |
| R2-2200776 | Considerations on CP issues | Lenovo, Motorola Mobility |
| R2-2200784 | Further Issues on Paging in NR Sidelink Relay | Nokia, Nokia Shanghai Bell |
| R2-2200794 | Discussion on establishment cause of relay UE | Xiaomi, Lenovo, Motorola Mobility, Apple |
| R2-2200795 | Discussion on connection control | Xiaomi |
| R2-2200796 | Discusson on SI delivery | Xiaomi |
| R2-2200855 | Control plane procedure | CMCC |
| R2-2200908 | Area specific SI issue in L2 relay | Sony |
| R2-2200946 | Discussion on RAN sharing with L2 U2N relays | Nokia, Nokia Shanghai Bell |
| R2-2201136 | Discussion on remaining issues on control plane procedures | Apple |
| R2-2201144 | Remaining Aspects of Paging and System Information for L2 UE to NW Relays | InterDigital |
| R2-2201145 | Open Issues on Connection Establishment for UE to NW Relays | InterDigital |
| R2-2201146 | IDLE/INACTIVE Remote UE Behaviour during Remote and Relay UE Mobility | InterDigital |
| R2-2201158 | Remaining issues on control plane for L2 sidelink relay | Ericsson |
| R2-2201218 | Consideration on the remain issues for control plane procedures | LG Electronics France |
| R2-2201294 | Access control support for U2N relaying | Intel Corporation |
| R2-2201345 | Consideration on the control plane procedure of SL relay | ZTE, Sanechips |
| R2-2201407 | Summary of AI 8.7.2.1 on CP procedure | OPPO |
| R2-2201509 | SI forwarding and paging for L2 sidelink relay | Huawei, HiSilicon |
| R2-2201510 | RRC connection management for L2 sidelink relay | Huawei, HiSilicon |
| R2-2201762 | Summary of [618] | OPPO |
| R2-2201778 | Summary of [AT116bis-e][608][Relay] RAN sharing (Huawei) | Huawei, HiSilicon |
| R2-2201810 | LS on support of RAN sharing and discovery signalling | RAN2 |
| R2-2201936 | Summary of [618] | OPPO |
| 8.7.2.2 | Service continuity | |
| R2-2200009 | Summary of [Post116-e][604][Relay] Remaining issues on service continuity (Xiaomi) | Xiaomi |
| R2-2200167 | Leftover Issues on Service Continuity for L2 U2N Relay | CATT |
| R2-2200174 | Remaining issues on service continuity of L2 U2N relay | Qualcomm Incorporated |
| R2-2200227 | Remaining issues for service continuity in L2 U2N relaying | Intel Corporation |
| R2-2200333 | Remaining issues for service continuity | MediaTek Inc. |
| R2-2200402 | Further discussions on open issues of path switch | NEC Corporation |
| R2-2200472 | Remaining issues on service continuity in L2 U2N relay | vivo |
| R2-2200488 | Discussion on remaining issue of service continuity | OPPO |
| R2-2200513 | Discussion on service continuity for L2 UE-to-Network relay | China Telecom |
| R2-2200654 | Open issues for service continuity | Samsung |
| R2-2200744 | Local remote UE ID allocation for direct to indirect path switching | ASUSTeK |
| R2-2200745 | Multiple PDU sessions handling during direct to indirect path switching | ASUSTeK |
| R2-2200777 | Path switching in L2 U2N relay case | Lenovo, Motorola Mobility |
| R2-2200793 | Discussion on service continuity | Xiaomi |
| R2-2200909 | Service continuity open issues in L2 NR sidelink relay | Sony |
| R2-2201056 | Remaining issues for Service Continuity in L2 relay | Kyocera |
| R2-2201137 | Discussion on remaining issues on service continuity | Apple |
| R2-2201147 | Remaining Issues on Service Continuity for L2 UE to NW Relays | InterDigital |
| R2-2201159 | Remaining Issues on Service Continuity for L2 Sidelink relay | Ericsson |
| R2-2201246 | Remaining issues on direct-to-indirect path switching | Sharp |
| R2-2201346 | Discussion on remaining issues on service continuity | ZTE, Sanechips |
| R2-2201444 | Service continuity in direct-to-indirect path switch | LG Electronics France |
| R2-2201462 | Support of idle mode mobility for remote-UE in SL UE-to-Nwk relay | Nokia, Nokia Shanghai Bell |
| R2-2201511 | Remaining issues on service continuity for L2 UE to NW Relay | Huawei, HiSilicon |
| R2-2201764 | [AT116bis-e][615] Support of idle/inactive relay UE in path switch (Intel) | Intel Corporation |
| R2-2201766 | [AT116bis-e][615] Support of idle/inactive relay UE in path switch (Intel) | Intel Corporation |
| 8.7.2.3 | Adaptation layer design | |
| R2-2200168 | Leftover Issues on Adaptation Layer Design for L2 U2N Relay | CATT |
| R2-2200175 | Remaining issues on adaptation layer of L2 U2N relay | Qualcomm Incorporated |
| R2-2200228 | Open aspects of adaptation layer design for L2 U2N relaying | Intel Corporation |
| R2-2200335 | Remaining issues for Adaptation layer design | MediaTek Inc. |
| R2-2200363 | Left issues for adaptation layer | OPPO |
| R2-2200473 | Adaptation Layer for Uu and PC5 | vivo |
| R2-2200556 | SRAP layer open issues for L2 U2N relay | Huawei, HiSilicon |
| R2-2200567 | Remaining issues related to SRAP | Fujitsu |
| R2-2200655 | Flow control for L2 U2N Relay | Samsung, Philips |
| R2-2200856 | Leftover issues on adaption layer design | CMCC |
| R2-2200937 | Remaining issues of the adaptation layer | Ericsson |
| R2-2200943 | summary of AI 8.7.2.3 on the adaptation layer | Ericsson |
| R2-2201347 | Discussion on adaptation layer design | ZTE, Sanechips |
| R2-2201465 | Remote ID for the adaptation layer | Nokia, Nokia Shanghai Bell |
| R2-2201492 | Remote UE local ID in PC5 Adaptation Layer Header | Beijing Xiaomi Mobile Software |
| R2-2201533 | Finalizing design of Adapt layer | Samsung Electronics GmbH |
| R2-2201831 | Summary of [AT116bis-e][619][Relay] Remaining proposals on adaptation layer (Ericsson) | Ericsson |
| 8.7.2.4 | QoS | |
| R2-2200169 | Leftover Issues on QoS Management for L2 U2N Relay | CATT |
| R2-2200334 | Remaining issues for QoS | MediaTek Inc. |
| R2-2200413 | Considerations on voice and video support for Relays | Philips International B.V., MediaTek, Vivo, FirstNet, KPN, TNO, Kyocera |
| R2-2200474 | Left issues on E2E QoS management | vivo |
| R2-2200656 | QoS handling for SL discovery | Samsung |
| R2-2200936 | Aspects for QoS management with SL relay | Ericsson |
| R2-2200995 | Remaining Issues in QoS for L2 Sidelink Relay | Fraunhofer IIS, Fraunhofer HHI |
| R2-2201148 | Discussion on QoS for L2 UE to NW Relays | InterDigital, Philips, Apple |
| R2-2201199 | Remaining issues on QoS | Huawei, HiSilicon |
| R2-2201348 | Discussion on QoS of SL relay | ZTE, Sanechips |
| R2-2201659 | Summary of agenda item 8.7.2.4 (QoS) | Samsung |
| 8.7.3.1 | Discovery | |
| R2-2200170 | Leftover Issues for Sidelink Discovery | CATT |
| R2-2200176 | Remaining issues on discovery | Qualcomm Incorporated |
| R2-2200229 | Discovery open aspects for U2N relaying | Intel Corporation |
| R2-2200411 | Relay Discovery in L2 and L3 relay case | Lenovo, Motorola Mobility |
| R2-2200475 | Remaining Issues of Discovery Message Transmission | vivo |
| R2-2200486 | Discussion on remaining issue of sidelink discovery | OPPO |
| R2-2200514 | Discussion on SL discovery remaining issues | China Telecom |
| R2-2200657 | PDCP and RLC aspects for SL discovery | Samsung |
| R2-2200934 | Left issues for SL discovery | Ericsson |
| R2-2201138 | Discussion on remaining issues on relay discovery | Apple |
| R2-2201149 | Using Shared and Dedicated Resource Pools for Discovery | InterDigital |
| R2-2201343 | Further discussion on Relay discovery | ZTE, Sanechips |
| R2-2201491 | Tx Resource Pools for Discovery | Beijing Xiaomi Mobile Software |
| R2-2201512 | Remaining issues on relay discovery | Huawei, HiSilicon |
| R2-2201763 | Summary of [AT116bis-e][609][Relay] Open Issues on Discovery (InterDigital) | InterDigital |
| R2-2201779 | LS to SA2 on discovery and data associated to different L2 IDs | vivo |
| R2-2201780 | LS to SA2 on discovery and data associated to different L2 IDs | RAN2 |
| 8.7.3.2 | Relay re/selection | |
| R2-2200171 | Leftover Issues for Relay Reselection | CATT |
| R2-2200177 | Remaining issues on relay (re)selection | Qualcomm Incorporated |
| R2-2200422 | U2N Relay UE operation Threshold Conditions: Impact of UE Mobility | Philips International B.V., FirstNet, MediaTek, Lenovo, Motorola Mobility |
| R2-2200476 | Remaining issues on Relay (re)selection | vivo |
| R2-2200487 | Discussion on remaining issues of NR sidelink relay (re)selection | OPPO |
| R2-2200626 | Left issues on NotificationMessageSidelink message | Spreadtrum Communications |
| R2-2200778 | Relay (re)selection for L2 and L3 relay | Lenovo, Motorola Mobility |
| R2-2200935 | Aspects for SL relay selection and reselection | Ericsson |
| R2-2201198 | Discussion on relay reselection aspects | Huawei, HiSilicon |
| R2-2201344 | Further discussion on Relay selection | ZTE, Sanechips |
| 8.8.1 | Organizational | |
| R2-2200055 | List of open issues for RAN slicing WI | CMCC |
| R2-2200844 | Open issues list for RAN Slicing | CMCC |
| R2-2200972 | Report of [Post116-e][243][Slicing] Running NR RRC CR for RAN slicing (Huawei) | Huawei |
| R2-2200973 | Running NR RRC CR for RAN slicing | Huawei, HiSilicon |
| R2-2201536 | 38.321 running CR for RAN Slicing | OPPO |
| R2-2201730 | [Post116bis-e][203][Slicing] Open issues for RAN slicing (CMCC) | CMCC |
| R2-2201974 | Draft stage 2 CR: Enhancements in RAN slicing | Nokia, Nokia Shanghai Bell |
| R2-2201980 | 38.321 running CR for RAN Slicing | OPPO |
| R2-2201987 | Running NR RRC CR for RAN slicing | Huawei, HiSilicon |
| 8.8.2 | Cell reselection | |
| R2-2200043 | [Post116-e][242][Slicing] Slice-based cell re-selection algorithm | Ericsson |
| R2-2200044 | Running 38.304 CR for RAN slicing | Ericsson |
| R2-2200179 | Remaining issues on slice specific cell reselection | Qualcomm Incorporated |
| R2-2200406 | Optimizations for signalling Slice Information | Lenovo, Motorola Mobility |
| R2-2200407 | RAN Slicing CR to 38.304 | Lenovo, Motorola Mobility |
| R2-2200408 | Triggers for initiating RAN slicing based cell reselections | Lenovo, Motorola Mobility |
| R2-2200409 | Principles of Slice based reselection | Lenovo, Motorola Mobility |
| R2-2200416 | Discussion on Slice based Cell Reselection | CATT |
| R2-2200417 | Analysis on issues of slice groups at TA boundaries | CATT |
| R2-2200510 | Further considerations of slice based cell reselection | Intel Corporation |
| R2-2200636 | Consideration on slice based cell reselection | Spreadtrum Communications |
| R2-2200845 | Discussion on open issues for slice based cell reselection | CMCC |
| R2-2200929 | Consideration on slice-specific cell reselection | OPPO |
| R2-2200947 | Considerations on slice groups | Nokia, Nokia Shanghai Bell |
| R2-2200948 | Text Proposals for the draft 38.304 PCR | Nokia, Nokia Shanghai Bell |
| R2-2200949 | Cell reselection delay for option B and option C | Samsung R&D Institute India |
| R2-2200974 | Discussion on slice based cell reselection under network control | Huawei, HiSilicon |
| R2-2201005 | Leftover issues in slice based cell reselection | ZTE corporation, Sanechips |
| R2-2201110 | Text proposal for slice based cell reselection under NW control | Apple |
| R2-2201169 | On slice-based cell re-selection TP for 38.304 | Ericsson |
| R2-2201190 | Slice-Info provision | NEC Telecom MODUS Ltd. |
| R2-2201192 | Slice-based cell re-selection TP for solution 4C | NEC Telecom MODUS Ltd. |
| R2-2201200 | Slice information provided by RRCRelease | Sharp |
| R2-2201208 | Discussion on signalling slice information | LG Electronics UK |
| R2-2201209 | Discussion on slice based cell reselection | LG Electronics UK |
| R2-2201389 | A couple of FFS for Cell Reselection | Kyocera |
| R2-2201406 | Discussion on Slice Aware UL BSR | RadiSys, Reliance JIO |
| R2-2201410 | Resolving the common issues in slice based cell reselection | Beijing Xiaomi Software Tech |
| R2-2201418 | TP for system information and slice based reselection priority handling | ZTE corporation, Sanechips |
| R2-2201422 | On selection of Solution 4 Option A, B and C | Samsung R&D Institute UK |
| R2-2201443 | Remaining Issues on Slice Information | Samsung R&D Institute UK |
| R2-2201686 | Text proposal for slice based cell reselection under NW control | Apple, BT Plc |
| R2-2201708 | Report for [AT116bis-e][240][Slicing] Remaining details for slice groups (CMCC) | CMCC |
| 8.8.3 | RACH | |
| R2-2200180 | Remaining issues on slice specific RACH | Qualcomm Incorporated |
| R2-2200846 | Discussion on open issues for slice based RACH configuration | CMCC |
| R2-2200930 | Consideration on slice-specific RACH | OPPO |
| R2-2200975 | Discussion on slice based RACH configuration | Huawei, HiSilicon |
| R2-2201050 | Detailed RRC signalling for RACH prioritization configuration | Nokia, Nokia Shanghai Bell |
| R2-2201111 | Slice based RACH configuration | Apple |
| R2-2201170 | RACH for RAN slicing enhancement | Ericsson |
| R2-2201409 | Considerations on remaining issues for slice based RACH | Beijing Xiaomi Software Tech |
| R2-2201417 | Further consideration on slice specific RACH | ZTE corporation, Sanechips |
| R2-2201475 | Remaining issues on slice based RACH prioritization | LG Electronics Inc. |
| 8.8.4 | UE capabilities | |
| R2-2200181 | Further discussion on UE capability related to RAN slicing enhancement | Qualcomm Incorporated |
| R2-2200418 | Analysis on UE capability for RAN slicing enhancement | CATT |
| R2-2200511 | UE capability for Slicing enhancement | Intel Corporation |
| R2-2200697 | Considerations on UE capability for RAN slicing | Beijing Xiaomi Software Tech |
| R2-2200847 | Discussion on UE capability for RAN slicing enhancement | CMCC |
| R2-2200931 | Consideration on UE capability for Slicing | OPPO |
| R2-2200976 | Discussion on UE capabilities for RAN slicing | Huawei, HiSilicon |
| R2-2201171 | UE Capabilities for Slice- based Cell re-selection | Ericsson |
| 8.9.1 | Organizational | |
| R2-2200130 | LS on further agreements on RLM and BFD relaxation for UE Power Saving enhancements (R4-2120314; contact: vivo, MediaTek) | RAN4 |
| R2-2200591 | 38.304 Running CR for ePowSav | vivo |
| R2-2201157 | 38.300 running CR for introduction of UE power saving enhancements | Huawei, HiSilicon |
| R2-2201268 | Update of 38.331 running CR for ePowSav with RAN1#107-e inputs | CATT |
| R2-2201476 | [Draft] LS on network control over the use of PEI | Futurewei Technologies |
| R2-2201724 | 38.331 running CR for introduction of UE power saving enhancements | CATT |
| R2-2201814 | 38.331 running CR for introduction of UE power saving enhancements | CATT |
| R2-2201988 | 38.304 Running CR for ePowSav | vivo |
| 8.9.2.1 | Paging Sub-grouping and Paging Early Indication | |
| R2-2200197 | UE Identity based Paging Subgrouping Aspects | Samsung Electronics Co., Ltd |
| R2-2200198 | UE Identity for paging subgrouping with eDRX | Samsung Electronics Co., Ltd |
| R2-2200199 | Simultaneous support of UE Identity based and CN assigned Paging Subgrouping | Samsung Electronics Co., Ltd |
| R2-2200239 | Discussion on paging subgrouping | OPPO |
| R2-2200315 | Open Issues for PEI and UE Paging Subgrouping | MediaTek Inc. |
| R2-2200455 | Remaining open issues on subgrouping | Intel Corporation |
| R2-2200464 | Discussing on Paging Sub-grouping and Paging Early Indication | Beijing Xiaomi Mobile Softwar |
| R2-2200592 | Discussion on remaining issues on PEI and sub-grouping | vivo |
| R2-2200898 | Considerations on remaining issues for paging subgrouping | CMCC |
| R2-2200899 | Further considerations on UE assistance information | CMCC |
| R2-2200910 | Discussion on paging subgrouping enhancements for idle/inactive-mode UE power saving | Sony |
| R2-2201102 | On some remaining issues in 38.304 running CR for ePowSav | Futurewei Technologies |
| R2-2201153 | Remaining issues on CN controlled subgrouping | Huawei, HiSilicon,CMCC |
| R2-2201155 | PEI configuration and monitoring | Huawei, HiSilicon |
| R2-2201219 | Further Consideration on Paging Subgrouping | ZTE Corporation,Sanechips |
| R2-2201221 | Consideration on the UE capability for Paging Enhancement | ZTE Corporation,Sanechips |
| R2-2201269 | Consideration on Paging Sub-grouping | CATT |
| R2-2201289 | Discussion on coexistence of paging subgroup and multicast paging | LG Electronics |
| R2-2201290 | Remaining issues on paging subgrouping | LG Electronics |
| R2-2201332 | PEI monitoring area | DENSO CORPORATION |
| R2-2201339 | Remaining details on subgrouping | Nokia, Nokia Shanghai Bell |
| R2-2201463 | On network control over the use of PEI | Futurewei Technologies |
| R2-2201541 | On the co-existence of UE-ID and CN assigned subgroups | Interdigital, Inc. |
| R2-2201542 | UE assistance for CN assigned subgroups | Interdigital, Inc. |
| R2-2201543 | Subgroup determination | Interdigital, Inc. |
| R2-2201555 | PEI in last used cell | Ericsson |
| R2-2201557 | Paging Early Indication and Subgroups | Ericsson |
| R2-2201675 | [Pre116bis][005][ePowSav] Summary of 8.9.2.1 Paging Sub-grouping and Paging Early Indication (MediaTek) | MediaTek |
| R2-2201785 | Summary of [Post116bis-e][080][ePowSav] Open Issues (Mediatek) | MediaTek Inc. |
| R2-2201916 | Summary of [AT116bis-e][054][ePowSav] Subgrouping and PEI | MediaTek Inc. |
| R2-2202053 | Summary of [Post116bis-e][089][IoT-NTN] Open Issues (Mediatek) | MediaTek |
| 8.9.2.2 | TRS/CSI-RS for idle/inactive | |
| R2-2200240 | Discussion on TRS/CSI-RS applicability for eDRX UEs | OPPO |
| R2-2200466 | Discussion on TRS CSI-RS for RRC-IDLE and RRC-INACTIVE State UE | Beijing Xiaomi Mobile Softwar |
| R2-2200593 | Discussion on TRS CSI-RS in idle inactive mode | vivo |
| R2-2201204 | R17 NR UE Power Save SIB-X sizing aspects | Apple |
| R2-2201220 | Further Consideration on TRS for Idle and Inactive UE | ZTE Corporation,Sanechips |
| R2-2201240 | Discussion on TRS/CSI-RS and eDRX | Sharp |
| R2-2201270 | TRS/CSI-RS for idle/inactive: leftover issues | CATT |
| R2-2201307 | Discussion on TRS/CSI-RS for idle/inactive | LG Electronics Finland |
| R2-2201497 | Potential TRS/CSI-RS occasion(s) | Nokia, Nokia Shanghai Bell |
| R2-2201556 | TRS exposure | Ericsson |
| R2-2201677 | Summary of 8.9.2.2 TRS/CSI-RS for idle/inactive (CATT) | CATT |
| R2-2201918 | Report of [AT116bis-e][055][ePowSav] TRS/CSI-RS for idle/inactive | CATT |
| 8.9.2.3 | RLM/BFD relaxation | |
| R2-2200186 | Issues on RLM-BFD relaxations | Qualcomm Incorporated |
| R2-2200241 | Discussion on RAN2’s impact of RLM/BFD relaxation | OPPO |
| R2-2200381 | Discussion on RLM_BFD measurement relaxation | NEC Europe Ltd |
| R2-2200451 | Further considerations for RLM/BFD relaxation | Intel Corporation |
| R2-2200465 | Discussion on RLM_BFD measurement relaxation | Beijing Xiaomi Mobile Softwar |
| R2-2200594 | Discussion on configurations of RLM/BFD relaxation for power saving | vivo |
| R2-2201156 | Discussion on RLM/BFD relaxation and DCI-based power saving adaptation | Huawei, HiSilicon |
| R2-2201271 | Consideration on RLM and BFD relaxation | CATT |
| R2-2201544 | RLM/BFD Relaxation Reporting | Interdigital, Inc. |
| R2-2201578 | Discussion on RLM/BFD Relaxation | LG Electronics Finland |
| R2-2201614 | On RLM/BFD relaxation | Nokia, Nokia Shanghai Bell |
| R2-2201684 | Summary of 8.9.2.3 RLM BFD relaxation | vivo |
| R2-2201941 | Summary of [AT116bis-e][056][ePowSav] RLM/BFD relaxation (vivo) | vivo |
| R2-2201942 | [Draft] LS to RAN4 on RLM BFD relaxation for ePowSav | vivo |
| R2-2201989 | LS to RAN4 on RLM/BFD relaxation for ePowSav | RAN2 |
| 8.9.2.4 | Other | |
| R2-2200187 | Enhancements for adaptive PDCCH monitoring | Qualcomm Incorporated |
| R2-2200188 | Subgrouping among paging occasions | Qualcomm Incorporated |
| R2-2200200 | PDCCH Skipping in RRC_CONNECTED | Samsung Electronics Co., Ltd |
| R2-2201222 | Initial Discussion on DCI based Power Saving | ZTE Corporation,Sanechips |
| R2-2201915 | Summary of [AT116bis-e][057][ePowSav] PDCCH Skip (Samsung) | Samsung Electronics Co., Ltd |
| R2-2201960 | LS on PDCCH Skipping in RRC_CONNECTED | RAN2 |
| 8.9.3 | UE Capabilities | |
| R2-2200242 | Discussion on UE capabilities | OPPO |
| R2-2200452 | UE capability for Rel-17 UE power saving | Intel Corporation |
| R2-2200453 | Draft running CR to 38331 on UE capabilities for Rel-17 UE power saving | Intel Corporation |
| R2-2200454 | Draft running CR to 38306 on UE capabilities for Rel-17 UE power saving | Intel Corporation |
| R2-2200463 | Discussing on UE capability for Paging enhancement | Beijing Xiaomi Mobile Softwar |
| R2-2200595 | Discussion on capabilities for ePowSav | vivo |
| R2-2201154 | UE capability design for paging subgrouping | Huawei, HiSilicon |
| R2-2201205 | R17 NR UE Power Save UE capability aspects | Apple |
| R2-2201340 | RAN2 impact on connected mode power saving | Nokia, Nokia Shanghai Bell |
| R2-2201681 | Summary of AI 8.9.3: UE capabilities | Intel |
| R2-2201910 | Report of [AT116bis-e][058][ePowSav] UE capabilities | Intel Corporation |
| 8.10.1 | Organizational | |
| R2-2200071 | Reply LS on UE TA reporting (R1-2112766; contact: Ericsson) | RAN1 |
| R2-2200104 | Reply LS on UE Location Aspects in NTN (R3-216067; contact: Ericsson) | RAN3 |
| R2-2200128 | Reply LS on Multiple SMTCs for NR NTN (R4-2120308; contact: Qualcomm) | RAN4 |
| R2-2200129 | LS on NR NTN Neighbor Cell and Satellite Information (R4-2120309; contact: Qualcomm) | RAN4 |
| R2-2200145 | LS on TAC reporting in ULI and support of SAs and FAs for NR Satellite Access (S2-2109337; contact: Qualcomm) | SA2 |
| R2-2200148 | Reply LS on NTN specific User Consent (S3-214349; contact: Qualcomm) | SA3 |
| R2-2200149 | Reply LS on UE location aspects in NTN (S3-214360; contact: CATT) | SA3 |
| R2-2200150 | Reply LS on UE location aspects in NTN (S3-214394; contact: Xiaomi) | SA3 |
| R2-2200449 | [Draft] Reply LS on Multiple SMTCs for NR NTN | Qualcomm Incorporated |
| R2-2200450 | [Draft] Reply LS on NR NTN Neighbor Cell and Satellite Information | Qualcomm Incorporated |
| R2-2200886 | Updated NR-NTN-solutions work plan | THALES |
| R2-2200887 | NR-NTN Stg2 running CR | THALES |
| R2-2201002 | Stage-3 running 304 CR for NTN | ZTE corporation, Sanechips |
| R2-2201006 | Stage-3 running 304 CR for NTN | ZTE corporation, Sanechips |
| R2-2201166 | MAC open issues in NTN - RAN2#116bis-e | InterDigital |
| R2-2201167 | Stage 3 NTN running CR for 38.321 - RAN2#116bis-e | InterDigital |
| R2-2201405 | DRAFT Reply LS on TAC reporting in ULI and support of SAs and FAs for NR Satellite Access | China Telecommunications |
| R2-2201433 | Stage-3 running RRC CR for NTN Rel-17 | Ericsson |
| R2-2201740 | [Draft] Reply LS on NTN specific User Consent | Qualcomm Inc. |
| R2-2201741 | Reply LS on Multiple SMTCs for NR NTN | Qualcomm Incorporated |
| R2-2201742 | Reply LS on NR NTN Neighbor Cell and Satellite Information | Qualcomm Incorporated |
| R2-2201754 | Reply LS on NTN specific User Consent | RAN2 |
| R2-2201883 | Reply LS on Multiple SMTCs for NR NTN | RAN2 |
| R2-2201884 | Reply LS on NR NTN Neighbor Cell and Satellite Information | RAN2 |
| R2-2201894 | Support of Non-Terrestrial Networks | THALES |
| R2-2201895 | Stage-3 running RRC CR for NTN Rel-17 | Ericsson |
| R2-2201896 | NTN RRC open issues towards RAN2#117 | Ericsson |
| R2-2201897 | Stage-3 running 304 CR for NTN | ZTE corporation, Sanechips |
| R2-2201898 | List of 38.304 open issues (ZTE) | ZTE corporation, Sanechips |
| R2-2201899 | Stage-3 running CR for TS 38.321 for Rel-17 NTN | InterDigital |
| R2-2201900 | MAC open issues in NTN | InterDigital |
| 8.10.2.1 | RACH aspects | |
| R2-2200214 | Discussion on remaining issues on TA reporting | Intel Corporation |
| R2-2200243 | Discussion on RACH and TA report in NTN | OPPO |
| R2-2200270 | Remaining issues related to TA report | Xiaomi |
| R2-2200347 | Remaining issues about RACH and TA reporting | Huawei, HiSilicon |
| R2-2200377 | Discussion on UE specific TA reporting | vivo |
| R2-2200520 | Consideration of TA report remaining issues of NTN | China Telecom |
| R2-2200627 | TA report procedure | Spreadtrum Communications |
| R2-2200688 | The Left Issues on UE-specific TA information reporting in NTN | CATT |
| R2-2200746 | Discussion on TA report during RA procedure | ASUSTeK |
| R2-2200747 | Discussion on issue of restarting contention resolution timer | ASUSTeK |
| R2-2200764 | Further discussion on TA reporting in NTN | Lenovo, Motorola Mobility |
| R2-2200876 | Considerations on RACH aspects | CMCC |
| R2-2201007 | Discussion on RACH open issues and TA reporting aspects | Nokia, Nokia Shanghai Bell |
| R2-2201034 | Further considerations on TA reporting | Samsung Research America |
| R2-2201164 | UE-specific TA reporting and other RACH aspects | InterDigital |
| R2-2201193 | Remaining issues on TA Report | NEC Telecom MODUS Ltd. |
| R2-2201324 | Consideration on remaining issues of RACH aspects | ZTE Corporation, Sanechips |
| R2-2201363 | Discussion on RACH and TA report aspects | LG Electronics Inc. |
| R2-2201630 | Reporting information about UE specific TA pre-compensation in NTNs | Ericsson |
| R2-2201656 | [Pre116bis-e][101][NTN] Summary of 8.10.2.1 RACH aspects (OPPO) | OPPO |
| R2-2201736 | Summary of [AT116bis][101][NTN] RACH aspects (OPPO) | OPPO |
| R2-2201746 | Summary of [AT116bis][101][NTN] RACH aspects (OPPO) | OPPO |
| R2-2201755 | Summary of [AT116bis][101][NTN] RACH aspects (OPPO) | OPPO |
| 8.10.2.2 | Other MAC aspects | |
| R2-2200244 | Remaining issues on other MAC aspects in NTN | OPPO |
| R2-2200271 | Remaining issues related to HARQ retransmission state | Xiaomi |
| R2-2200348 | Remaining issues about other MAC aspects | Huawei, HiSilicon |
| R2-2200444 | HARQ process for SPS and CG | Qualcomm Incorporated |
| R2-2200618 | Remaining issues on disabling uplink HARQ retransmission | MediaTek Inc. |
| R2-2200619 | Round trip delay offset for configured grant timer | MediaTek Inc. |
| R2-2200628 | Discussion on HARQ and LCP remaining issues | Spreadtrum Communications |
| R2-2200689 | Left Issues on DL/UL HARQ Aspects | CATT |
| R2-2200787 | Remaining issues on HARQ related timer handling for NR NTN | vivo |
| R2-2200788 | Remaining issues on LCP aspects | vivo |
| R2-2200870 | Further Considerations on CG/SPS for NR NTN | CMCC |
| R2-2200911 | CG enhancements in NTN | Sony |
| R2-2201008 | Discussion on left issues on MAC aspects | Nokia, Nokia Shanghai Bell |
| R2-2201163 | Remaining MAC open issues in NTN | InterDigital |
| R2-2201325 | Consideration on remaining issues of other MAC aspects | ZTE Corporation, Sanechips |
| R2-2201364 | Discussion on other MAC aspects | LG Electronics Inc. |
| R2-2201480 | HARQ State A/B for CG/SPS aspects | ITL |
| R2-2201629 | On configured scheduling, DRX, LCP, HARQ and SR/BSR in NTNs | Ericsson |
| R2-2201739 | Summary of [AT116bis-e][107][NTN] Other MAC aspects | InterDigital |
| R2-2201749 | Summary of [AT116bis-e][107][NTN] Other MAC aspects: Phase 2 | InterDigital (summary rapporteur) |
| 8.10.2.3 | RLC and PDCP aspects | |
| R2-2201194 | RLC t-Reassembly timer | NEC Telecom MODUS Ltd. |
| 8.10.3.1 | General aspects | |
| R2-2200212 | Discussion on location reporting | Intel Corporation |
| R2-2200245 | Discussion on UE location information reporting | OPPO |
| R2-2200289 | Discussion on UE location reporting | Huawei, HiSilicon |
| R2-2200445 | Discussion on coarse UE location report | Qualcomm Incorporated |
| R2-2200629 | Discussion on TAC update and LCS in NTN | Spreadtrum Communications |
| R2-2200715 | Discussion on UE location reporting in NTN | Xiaomi |
| R2-2200748 | Discussion on event triggered based UE location report | ASUSTeK |
| R2-2200869 | Views on UE Location Information Reporting in NTN | CMCC |
| R2-2200879 | UE location during initial access | THALES |
| R2-2200912 | Event triggered location reporting in NTN | Sony |
| R2-2200960 | Reporting virtual location identifier for AMF/PLMN selection and location verification in NTN | Fraunhofer IIS; Fraunhofer HHI; Thales |
| R2-2200987 | On reporting of UE location information | ZTE corporation, Sanechips |
| R2-2201080 | On LCS and TAC handling in Rel-17 NTN | Nokia, Nokia Shanghai Bell |
| R2-2201178 | On UE location reporting in NTN | Apple |
| R2-2201404 | Discussion of reply LS on TAC reporting in NTN | China Telecom |
| R2-2201408 | Discussion on left issues on UE location report | CATT |
| R2-2201445 | General aspects for NTN | Ericsson |
| R2-2201447 | Remaining issues on TAC selection and reporting in NTN | Samsung R&D Institute UK |
| R2-2201579 | UE location reporting in initial access | Samsung Research America |
| R2-2201743 | [offline-110] UE location during initial access | Thales |
| R2-2201744 | LS on UE location during initial access in NTN | Thales |
| R2-2201881 | LS on UE location during initial access in NTN | RAN2 |
| R2-2201929 | LS on UE location during initial access in NTN | Thales |
| 8.10.3.2 | Idle/Inactive mode | |
| R2-2200215 | Discussion on TN prioritization over NTN for idle mode | Intel Corporation |
| R2-2200216 | Discussion on enhancements to cell reselection | Intel Corporation |
| R2-2200246 | Discussion on NTN specific system information | OPPO |
| R2-2200290 | Discussion on idle mode aspects | Huawei, HiSilicon |
| R2-2200342 | System information to assist cell reselection | ITRI |
| R2-2200378 | Remaining issues on idle/inactive mode mobility | vivo |
| R2-2200446 | Cell type indication | Qualcomm Incorporated |
| R2-2200447 | IDLE mode measurements | Qualcomm Incorporated |
| R2-2200621 | Idle mode mobility for NTN-TN scenarios | MediaTek Inc. |
| R2-2200630 | Acquiring the ephemeris of neighbour cell | Spreadtrum Communications |
| R2-2200650 | Discussion on NTN Idle mode measurement and cell reselection | Transsion Holdings |
| R2-2200665 | Remaining idle mode issues in NTN | LG Electronics Inc. |
| R2-2200690 | Further Discussion on the Leftover Issues of IDLE/INACTIVE | CATT |
| R2-2200716 | Discussion on RRC idle mode issues | Xiaomi |
| R2-2200766 | Ephemeris provision in system information for NTN | Lenovo, Motorola Mobility |
| R2-2200767 | Further discussion on idle mode mobility in NTN | Lenovo, Motorola Mobility |
| R2-2200877 | Further Considerations on Cell Re-selection | CMCC |
| R2-2200933 | SMTC Adjustment for Idle and Inactive UEs in NTN | Google Inc. |
| R2-2201003 | System information for NTN and idle mode mobility for intra-NTN and TN-NTN case | ZTE corporation, Sanechips |
| R2-2201079 | On IDLE mode aspects in Rel-17 NTN | Nokia, Nokia Shanghai Bell |
| R2-2201139 | On Defining a New NTN-Specific SIB | MediaTek Inc. |
| R2-2201165 | Location-assisted cell reselection | InterDigital |
| R2-2201179 | NTN-TN idle mode mobility | Apple |
| R2-2201180 | NTN Ephemeris definition and signaling | Apple |
| R2-2201195 | Location-assisted cell reselection | NEC Telecom MODUS Ltd. |
| R2-2201196 | NTN to TN mobility in Idle or Inactive mode | NEC Telecom MODUS Ltd. |
| R2-2201446 | Idle mode aspects for NTN | Ericsson |
| R2-2201580 | Measurements and cell reselection | Samsung Research America |
| R2-2201615 | Discussion on system information enhancement for NR NTN | Turkcell, BT Plc, Deutsche Telekom, Aselsan |
| R2-2201731 | [Pre116bis-e][102][NTN] Summary of 8.10.3.2 Idle/Inactive mode | Huawei, HiSilicon |
| R2-2201733 | Summary of [AT116bis-e][102][NTN] Idle/Inactive mode aspects (Huawei) | Huawei, HiSilicon |
| R2-2201745 | Summary of [AT116bis-e][102][NTN] Idle/Inactive mode aspects – Second round (Huawei) | Huawei, HiSilicon |
| R2-2201756 | Summary of [AT116bis-e][102][NTN] Idle/Inactive mode aspects – third round (Huawei) | Huawei, HiSilicon |
| R2-2201757 | LS on NTN-specific SIB | RAN2 |
| R2-2201938 | draft LS on system information | Huawei |
| 8.10.3.3 | Connected mode | |
| R2-2200247 | Discussion on NTN UE capabilities | OPPO |
| R2-2200666 | Connected mode remaining issues in NTN | LG Electronics Inc. |
| R2-2200765 | Remaining CHO issues in RRC running CR | Lenovo, Motorola Mobility |
| R2-2200913 | SMTC enhancement in NTN | Sony |
| R2-2201004 | Leftover issues in CHO and measurements | ZTE corporation, Sanechips |
| 8.10.4 | UE capabilities | |
| R2-2200040 | Report of email discussion [Post116-e][111][NTN] UE capabilities (Intel) | Intel Corporation |
| R2-2200041 | Draft 331 CR for NR NTN UE capabilities | Intel Corporation |
| R2-2200042 | Draft 306 CR for NR NTN UE capabilities | Intel Corporation |
| R2-2200213 | Discussion on remaining issues on NR NTN UE capabilities | Intel Corporation |
| R2-2200291 | Discussion on UE capabilities | Huawei, HiSilicon |
| R2-2200376 | Remaining issues on UE capability for Rel-17 NTN | vivo |
| R2-2200448 | Discussion on UE capabilities | Qualcomm Incorporated |
| R2-2200620 | On UE Capabilities in NR-NTN | MediaTek Inc. |
| R2-2201545 | L2 buffer calculation and QoS requirement | Interdigital, Inc. |
| R2-2201632 | NR NTN UE capabilities | Ericsson |
| R2-2201748 | Report of email discussion [AT116bis-e][112][NTN] Capabilities (Intel) | Intel Corporation |
| R2-2201961 | Draft 331 CR for NR NTN UE capabilities | Intel Corporation |
| R2-2201962 | List of open issues on NR NTN UE capabilities | Intel Corporation |
| R2-2201969 | Draft 306 CR for NR NTN UE capabilities | Intel Corporation |
| 8.11.1 | Organizational | |
| R2-2200074 | LS on latency improvement for PRS measurement with MG (R1-2112784; contact: Huawei) | RAN1 |
| R2-2200082 | LS on TRP beam/antenna information (R1-2112844; contact: Ericsson) | RAN1 |
| R2-2200083 | LS on configuration and transmission of SRS for positioning in RRC_INACTIVE state (R1-2112846; contact: Intel) | RAN1 |
| R2-2200089 | LS on PRS processing window (R1-2112881; contact: Huawei) | RAN1 |
| R2-2200092 | LS on the reporting of the Tx TEG association information (R1-2112968; contact: CATT) | RAN1 |
| R2-2200113 | Reply LS on location estimates in local co-ordinates (R3-216235; contact: Huawei) | RAN3 |
| R2-2200139 | Reply LS on Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance (S2-2109104; contact: Huawei) | SA2 |
| R2-2200140 | Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance (S2-2109105; contact: CATT) | SA2 |
| R2-2200282 | Running 38.305 CR for Positioning WI on RAT dependent positioning methods | Intel Corporation |
| R2-2200284 | Rel-17 positioning capabilities | Intel Corporation |
| R2-2200285 | Open issue lists on Rel-17 positioning WI | Intel Corporation |
| R2-2200302 | [Draft]Reply LS on the Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance | CATT |
| R2-2200431 | Draft running CR for MAC spec in R17 positioning | Huawei, HiSilicon |
| R2-2200432 | Draft running CR for LTE RRC spec for GNSS integrity in R17 positioning | Huawei, HiSilicon |
| R2-2200523 | [Draft] Response LS on the latency improvement for PRS measurement with MG | ZTE |
| R2-2200524 | [Draft] Response LS on the PRS processing window | ZTE |
| R2-2200525 | [Draft] Response LS on the reporting of the Tx TEG association information | ZTE |
| R2-2200526 | [Draft] Response LS on the TRP beam antenna information | ZTE |
| R2-2200959 | Running LPP CR for NR positioning enhancements | Qualcomm Incorporated |
| R2-2201390 | Running CR of 36.305 for GNSS Positioning Integrity | InterDigital, Inc. |
| R2-2201391 | Running CR of 38.305 for GNSS Positioning Integrity | InterDigital, Inc. |
| R2-2201722 | Summary of [Post116bis-e][628][POS] 37.355 running CR (Qualcomm) | Qualcomm Incorporated |
| R2-2201723 | Running LPP CR for NR positioning enhancements | Qualcomm Incorporated |
| R2-2201767 | Report of offline discussion [AT116bis-e][610][POS] Positioning UE capabilities (Intel) | Intel Corporation |
| R2-2201782 | Reply LS on latency improvement for PRS measurement with MG | Nokia |
| R2-2201798 | Email discussion report on [Post116bis-e][627][POS] 36.305/38.305 integrity running CRs (InterDigital) | InterDigital Inc. |
| R2-2201799 | Running CR of 36.305 for Positioning WI on GNSS Positioning Integrity | InterDigital, Inc. |
| R2-2201800 | Running CR of 38.305 for Positioning WI on GNSS Positioning Integrity | InterDigital, Inc. |
| R2-2201815 | Running 38.305 CR for Positioning WI on RAT dependent positioning methods | Intel Corporation |
| R2-2202005 | Report of email discussion [Post116bis-e][634][POS] Positioning open issues list (Intel) | Intel Corporation |
| R2-2202011 | Introduction of R17 Positioning for MAC spec | Huawei, HiSilicon |
| R2-2202044 | Report for RRC RAT-dependent Positioning CR | Ericsson |
| R2-2202048 | Capturing RRC impacts for RAT dependent Positioning | Ericsson |
| R2-2202052 | Reply LS on latency improvement for PRS measurement with MG | RAN2 |
| 8.11.2 | Latency enhancements | |
| R2-2200256 | Discussion on positioning latency reduction | ZTE |
| R2-2200278 | Leftover issues on Latency reduction | Intel Corporation |
| R2-2200279 | RAN1 issues on Latency reduction | Intel Corporation |
| R2-2200304 | Discussion on latency reduction enhancement | CATT |
| R2-2200326 | Discussion on latency enhancement | vivo |
| R2-2200428 | Discussion on PRS preconfiguration | Huawei, HiSilicon |
| R2-2200430 | Discussion on MG/PPW enhancement for positioning | Huawei, HiSilicon |
| R2-2200559 | Further consideration of positioning latency enhancements | OPPO |
| R2-2200709 | Positioning enhancement on latency reduction. | Xiaomi |
| R2-2200730 | Discussion on the response time | Samsung |
| R2-2200914 | Considerations on positioning latency | Sony |
| R2-2200958 | Providing a list of AD for reducing signalling load and latency | Fraunhofer IIS; Fraunhofer HHI; Ericsson; Lenovo; Vivo |
| R2-2200962 | Remaining Issues on Scheduling Location in Advance | Qualcomm Incorporated |
| R2-2200988 | On Positioning Latency Reduction Enhancements | Lenovo, Motorola Mobility |
| R2-2201069 | Discussion On RRC and MAC Impacts, TP on RRC Impacts | Ericsson |
| R2-2201184 | Discussion on Enhancements for Latency Reduction | InterDigital, Inc. |
| R2-2201185 | Discussion on Measurement Gap and PRS Priority Enhancements | InterDigital, Inc. |
| R2-2201309 | Simulation study for multiple QoS class handling for latency reduction | Samsung R&D Institute UK |
| R2-2201311 | Handling of multiple QoS for latency reduction | Samsung R&D Institute UK |
| R2-2201312 | Latency reduction via new measurement gap activation | Samsung R&D Institute UK |
| R2-2201652 | Summary on agenda item 8.11.2 on Latency Enhancements | Qualcomm Incorporated |
| R2-2201875 | Summary of [AT116bis-e][616][POS] Remaining proposals on latency reduction | Qualcomm Incorporated |
| 8.11.3 | RRC_INACTIVE | |
| R2-2200257 | Discussion on positioning in RRC INACTIVE state | ZTE |
| R2-2200280 | Support of UL&UL+DL positioning in RRC_INACTIVE | Intel Corporation |
| R2-2200295 | Impact on SA2 with DL NR positioning in RRC_INACTIVE | CATT, Ericsson |
| R2-2200296 | Discussion on UL NR Positioning in RRC_INACTIVE state | CATT |
| R2-2200327 | Discussion on positioning in RRC_INACTIVE | vivo |
| R2-2200424 | Way-forward for RRC_INACTIVE positioning | Huawei, CATT, China Unicom, CMCC, Fraunhofer, Futurewei, HiSilicon, Intel Corporation, Spreadtrum Communications, OPPO, VIVO, Xiaomi, ZTE Corporation |
| R2-2200425 | Remaining issues on RRC_INACTIVE DL Postioning | Huawei, HiSilicon |
| R2-2200710 | Discussion on positioning for UE in RRC Inactive | Xiaomi |
| R2-2200731 | Discussion on the measurement reporting in RRC_INACTIVE | Samsung |
| R2-2200781 | Discussion on Positioning in RRC_INACTIVE state | OPPO |
| R2-2200957 | Remaining Details for RRC_INACTIVE Positioning in Uplink | Fraunhofer IIS; Fraunhofer HHI |
| R2-2200961 | [draft] LS on Positioning in RRC_INACTIVE State | Qualcomm Incorporated |
| R2-2200963 | Remaining issues for positioning of UEs in RRC_INACTIVE State | Qualcomm Incorporated |
| R2-2200989 | Remaining aspects on RRC_INACTIVE Positioning | Lenovo, Motorola Mobility |
| R2-2201065 | Discussion on RRC Inactive mode Positioning | Ericsson |
| R2-2201068 | Summary of AI 8.11.3 RRC_INACTIVE | Ericsson |
| R2-2201186 | Discussion on Positioning in RRC INACTIVE state | InterDigital, Inc. |
| R2-2201528 | Positioning in RRC_INACTIVE | Nokia Germany |
| R2-2201772 | [AT116bis-e][617][POS] Remaining issues on positioning in RRC_INACTIVE (Ericsson) | Ericsson |
| 8.11.4 | On-demand PRS | |
| R2-2200047 | Report on Procedures and signalling for on-demand PRS | Ericsson |
| R2-2200258 | Discussion on on-demand PRS | ZTE |
| R2-2200281 | Support of On-Demand PRS request | Intel Corporation |
| R2-2200303 | Discussion on on-demand PRS | CATT |
| R2-2200328 | Discussion on on-demand PRS | vivo |
| R2-2200426 | Discussion on on-demand PRS | Huawei, HiSilicon |
| R2-2200711 | Positioning enhancement about on-demand DL PRS | Xiaomi |
| R2-2200780 | Discussion on on-demand DL-PRS | OPPO |
| R2-2200915 | Considerations on positioning PRS On-demand and two stage beam sweeping | Sony |
| R2-2200956 | On-demand PRS | Fraunhofer IIS, Fraunhofer HHI |
| R2-2200964 | Remaining issues for on-demand DL-PRS | Qualcomm Incorporated |
| R2-2200993 | Remaining issues on On-Demand DL-PRS | Lenovo, Motorola Mobility |
| R2-2201067 | Remaining issues on On-demand PRS | Ericsson |
| R2-2201103 | On the need for additional On-Demand PRS enhancements | Apple |
| R2-2201187 | Discussion on On-demand PRS | InterDigital, Inc. |
| R2-2201257 | Network Control Mechanisms for On-demand PRS | Nokia, Nokia Shanghai Bell |
| R2-2201267 | On the on-demand PRS Stage 2 | Nokia, Nokia Shanghai Bell |
| R2-2201273 | Pre-configured and Pre-defined PRS | Nokia, Nokia Shanghai Bell |
| R2-2201313 | On-demand PRS request and configuration | Samsung R&D Institute UK |
| R2-2201627 | On-demand PRS | Fraunhofer IIS, Fraunhofer HHI |
| 8.11.5 | GNSS positioning integrity | |
| R2-2200012 | [Post116-e][602][POS] Stage 2 baseline for integrity assistance data (Swift) | Swift |
| R2-2200013 | Running CR on 36.305 for Stage 2 integrity assistance data | Swift |
| R2-2200014 | Running CR on 38.305 for Stage 2 integrity assistance data | Swift |
| R2-2200185 | Signalling for GNSS Positioning Integrity Framework | Nokia, Nokia Shanghai Bell |
| R2-2200259 | Discussion on positioning integrity | ZTE |
| R2-2200329 | Discussion on GNSS positioning integrity | vivo |
| R2-2200427 | Remaining issues on positioning integrity | Huawei, HiSilicon |
| R2-2200955 | UE-aided detection of threat to GNSS systems and assistance data signaling | Fraunhofer IIS; Fraunhofer HHI; Ericsson; ESA |
| R2-2201063 | On GNSS Integrity | Ericsson |
| R2-2201188 | Discussion on GNSS Positioning Integrity | InterDigital, Inc. |
| R2-2201214 | Stage 3 Proposals on GNSS Positioning Integrity | Swift Navigation, Mitsubishi Electric Corporation, Ericsson |
| R2-2201314 | Consideration on the signalling design for Positioning Integrity for UE-based method | Samsung R&D Institute UK |
| R2-2201761 | Report of [AT116bis-e][611][POS] GNSS integrity (Swift) | Swift Navigation |
| R2-2201765 | [AT116bis-e][611][POS] GNSS integrity - Extended Discussion (Stage 3) (Swift) | Swift Navigation |
| 8.11.6 | A-GNSS enhancements | |
| R2-2200298 | Introduction of B2a and B3I signal in BDS system in A-GNSS | CATT, CAICT |
| R2-2200433 | Draft running CR for stage2 spec for NAVIC in R17 positioning | Huawei, HiSilicon |
| R2-2201070 | Impacts of NavIC in NR RRC | Ericsson |
| R2-2201773 | Draft running CR for stage2 spec for NAVIC in R17 positioning | Huawei, HiSilicon |
| R2-2201774 | Introduction of NavIC for broadcast support | Ericsson |
| R2-2201775 | [AT116bis-e][613][POS] BDS and NavIC CRs (CATT) | CATT |
| 8.11.7 | Accuracy enhancements | |
| R2-2200283 | Support of PRU | Intel Corporation |
| R2-2200297 | Discussion on additional TRP beam/antenna information | CATT |
| R2-2200299 | Discussion on stage-2 impact of mitigating UE and TRP RxTx timing delays | CATT |
| R2-2200300 | Discussion on LPP and RRC signaling impact of mitigating UE and TRP RxTx timing delays | CATT |
| R2-2200301 | [Draft]Reply LS on the reporting of the Tx TEG association information | CATT |
| R2-2200330 | Discussion on accuracy enhancements | vivo |
| R2-2200429 | Discussion on accuracy enhancement | Huawei, HiSilicon |
| R2-2200438 | Summary of email discussion for PRU | Huawei, HiSilicon |
| R2-2200527 | Discussion on signalling support of RAN1 agreements | ZTE |
| R2-2200712 | Discussion on positioning reference unit | Xiaomi |
| R2-2200916 | Considerations on Timing Error aspects | Sony |
| R2-2200994 | Support of Positioning Reference Units | Lenovo, Motorola Mobility |
| R2-2201062 | LPP Positioning enhancements on timing errors , DL-AoD and LoS/NLoS/multipath | Ericsson |
| R2-2201064 | On the Positioning Reference Units aspects | Ericsson |
| R2-2201066 | Beam/antenna information for DL AOD in NR positioning | Ericsson |
| R2-2201087 | Way forward on PRUs for Rel-17 | MediaTek Inc., Apple |
| R2-2201104 | Signalling impacts of RAN1 agreements on accuracy enhancements | Apple |
| R2-2201189 | Discussion on Accuracy Enhancements | InterDigital, Inc. |
| R2-2201191 | Discussion on supporting Positioning Reference Units | InterDigital, Inc. |
| R2-2201360 | Discussion on accuracy improvement for UE-assisted DL-AOD positioning | vivo |
| R2-2201768 | Summary of [AT116bis-e][612][POS] Positioning accuracy enhancements (Apple) | Apple |
| R2-2201776 | Response LS on the reporting of the Tx TEG association information | RAN2 |
| R2-2201869 | Reply LS on the reporting of the Tx TEG association information | CATT |
| R2-2201870 | Accuracy enhancement TP for 38.305 | CATT |
| 8.11.8 | Other | |
| R2-2200331 | Discussion on positioning reference unit | vivo |
| R2-2200965 | On PRU support in Release-17 | Qualcomm Incorporated |
| 8.12.1 | Organizational | |
| R2-2200068 | Reply LS on capability related RAN2 agreements for RedCap (R1-2112754; contact: Ericsson) | RAN1 |
| R2-2200075 | LS on use of NCD-SSB or CSI-RS in DL BWPs for RedCap UE (R1-2112802; contact: Ericsson) | RAN1 |
| R2-2200131 | Reply LS on use of NCD-SSB for RedCap UE (R4-2120327; contact: ZTE) | RAN4 |
| R2-2201531 | Running 38300 CR for RedCap | Nokia, Nokia Shanghai Bell |
| R2-2201549 | Running CR for the RedCap WI | Ericsson |
| R2-2201564 | Running RRC CR for the RedCap WI | Ericsson |
| R2-2201649 | Running MAC CR for RedCap | vivo (Rapporteur) |
| R2-2201885 | Running 38300 CR for RedCap | Nokia, Nokia Shanghai Bell |
| R2-2201886 | Running CR for the RedCap WI | Ericsson |
| R2-2201887 | Open issue list for 38.331 for RedCap | Ericsson |
| R2-2201888 | Running CR for the RedCap WI | Ericsson |
| R2-2201889 | Open issue list for 38.304 for RedCap | Ericsson |
| R2-2201890 | Running MAC CR for RedCap | vivo (Rapporteur) |
| R2-2201891 | Open issue list on MAC for RedCap | vivo |
| R2-2201893 | Report of email discussion [Post116bis-e][105][RedCap] 38.306 running CR and list of open issues (Intel) | Intel Corporation |
| 8.12.2.1 | Definition of RedCap UE type and reduced capabilities | |
| R2-2200189 | Support for fallback operation by RedCap UEs | Qualcomm Incorporated |
| R2-2200248 | Discussion on RedCap UE's fallback operation | OPPO |
| R2-2200286 | Open issues on RedCap capabilities | Intel Corporation |
| R2-2200350 | Discussion on allowing RedCap UEs to be served as normal UEs | NEC Corporation |
| R2-2200553 | Definition and reduced capabilities for RedCap UE | Huawei, HiSilicon |
| R2-2200596 | Discussion on UE type and reduced capabilities for RedCap UEs | vivo, Guangdong Genius |
| R2-2200685 | Discussion on supporting fallback operation for Redcap UEs | CATT |
| R2-2200798 | RedCap UE access in legacy gNB | Ericsson |
| R2-2201114 | Optional support of more than 8 DRB for RedCap | Apple, Facebook Inc |
| R2-2201206 | Discussion on fallback operation of RedCap UEs | LG Electronics UK |
| R2-2201231 | Support for fallback operation by RedCap UEs | Sierra Wireless. S.A. |
| R2-2201434 | RedCap cell selection and cell reselection | BT Plc, Nokia, Nokia Shanghai Bell, Turkcell, Deutsche Telekom, Orange, Telecom Italia S.p.A. |
| R2-2201671 | Optional support of more than 8 DRB for RedCap | Apple, Facebook Inc, T-Mobile USA |
| R2-2201737 | Report of offline discussion [AT116bis-e][105][RedCap] Capabilities (Intel) | Intel Corporation |
| R2-2201750 | Report of offline discussion [AT116bis-e][105][RedCap] Capabilities (Intel) | Intel Corporation |
| R2-2201892 | Running 38.331 CR for the RedCap WI on capablities | Intel Corporation |
| R2-2201968 | Running 38.306 CR for the RedCap WI on capablities | Intel Corporation |
| 8.12.2.2 | Identification, access and camping restrictions | |
| R2-2200190 | Discussions on RedCap-specific BWPs | Qualcomm Incorporated |
| R2-2200208 | Cell barring aspects | Samsung Electronics Co., Ltd |
| R2-2200249 | Discussion on RedCap UE's identification and camping restrictions | OPPO |
| R2-2200287 | Open issues on Early identification, camping restrictions and NCD-SSB | Intel Corporation |
| R2-2200332 | Cell (re)selection details for RedCap UEs | Samsung Electronics |
| R2-2200343 | System Information and supporting for RedCap UEs | KDDI Corporation |
| R2-2200401 | BWP configuration for RedCap UE | DENSO CORPORATION |
| R2-2200468 | Discussion on UE access restrictions for Redcap devices | Beijing Xiaomi Mobile Softwar |
| R2-2200469 | Discussion on early Identification for Redcap devices | Beijing Xiaomi Mobile Softwar |
| R2-2200554 | Identification and access restriction of RedCap UE, and NCD-SSB related issues | Huawei, HiSilicon |
| R2-2200568 | Camping restrictions of RedCap UE | Fujitsu |
| R2-2200597 | Remaining issues on NCD SSB, identification and access for RedCap | vivo, Guangdong Genius |
| R2-2200608 | Discussion on separate initial BWP and NCD-SSB for RedCap UE | ZTE Corporation, Sanechips |
| R2-2200609 | On Access and Camping Restrictions | ZTE Corporation, Sanechips |
| R2-2200616 | Further considerations on access restrictions | NEC |
| R2-2200639 | Discussion on the open issues of identification and access restrictions for RedCap UE | Spreadtrum Communications |
| R2-2200686 | Discussion on the remaining issues of early identification and IFRI | CATT |
| R2-2200725 | Corrections for cellBarred in MIB handling for RedCap UE | InterDigital, Europe, Ltd. |
| R2-2200797 | Early indication & access restriction for RedCap UEs | Ericsson |
| R2-2200830 | Using NCD-SSB or CSI-RS in DL BWPs for RedCap UEs | Ericsson |
| R2-2200831 | [DRAFT] Reply LS on the use of NCD-SSB or CSI-RS in DL BWPs for RedCap UEs | Ericsson |
| R2-2200836 | NR-REDCAP access restriction/allowance indication to ease mobility | THALES |
| R2-2200861 | Discussion on access restrictions and early identification | CMCC |
| R2-2200862 | Discussion on use of NCD-SSB or CSI-RS in DL BWPs for RedCap UE | CMCC |
| R2-2201113 | RedCap UE power-saving aspects at cell re-selection | Apple |
| R2-2201207 | Discussion on identification and access restrictions for RedCap UEs | LG Electronics UK |
| R2-2201232 | Early identification and camping restrictions for RedCap UE | Sierra Wireless. S.A. |
| R2-2201237 | Neighbour cell information and cell (re)selection for RedCap UE | DENSO CORPORATION |
| R2-2201435 | Support and network behaviour for RedCap early indication messages | BT Plc, Deutsche Telekom AG, Telecom Italia S.p.A., TurkCell, CMCC, NTT DOCOMO INC., Orange, Vodafone |
| R2-2201461 | Aspects related to use of NCD-SSB | MediaTek Inc. |
| R2-2201587 | Further details of identification, access, and camping restrictions | Nokia, Nokia Shanghai Bell |
| R2-2201623 | Support and network behaviour for RedCap early indication messages | BT Plc, Deutsche Telekom AG, Telecom Italia S.p.A., TurkCell, CMCC, NTT DOCOMO INC., Orange, Vodafone, KDDI |
| R2-2201732 | Summary of NCD-SSB and Initial BWP aspects | Ericsson (Rapporteur) |
| R2-2201734 | Summary of [AT116bis-e][103][RedCap] Identification and access restriction (Huawei) | Huawei, HiSilicon |
| R2-2201738 | NCD-SSB and Initial BWP aspects | Ericsson (Rapporteur) |
| R2-2201751 | Summary of [AT116bis-e][103][RedCap] Identification and access restriction (Huawei) | Huawei, HiSilicon |
| R2-2201753 | NCD-SSB and Initial BWP aspects - second round | Ericsson (Rapporteur) |
| R2-2201759 | Reply LS on the use of NCD-SSB or CSI-RS in DL BWPs for RedCap Ues | RAN2 |
| R2-2201760 | LS on RSRP measurement before Msg1 or MsgA retransmission | RAN2 |
| 8.12.3.2 | RRM relaxations | |
| R2-2200191 | Remaining issues on RRM relaxation | Qualcomm Incorporated |
| R2-2200250 | Discussion on RRM relax | OPPO |
| R2-2200288 | Open issues on RRM measurement relaxation | Intel Corporation |
| R2-2200467 | Discussion on RRM measurement relaxation for redcap | Beijing Xiaomi Mobile Softwar |
| R2-2200549 | RRM measurement relaxation in RedCap | Samsung |
| R2-2200555 | RRM measurement relaxation for RedCap UE | Huawei, HiSilicon |
| R2-2200598 | RRM relaxation for neighboring cell | vivo, Guangdong Genius |
| R2-2200610 | Further discussion on RRM relaxation for RedCap UE | ZTE Corporation, Sanechips |
| R2-2200667 | Remaining issues in RRM relaxation | LG Electronics Inc. |
| R2-2200687 | Further Discussion on RRM Relaxations | CATT |
| R2-2201088 | On the need for a separate reference Srxlev value for evaluating R17 stationary criterion for RRM relaxation | Futurewei Technologies |
| R2-2201101 | On a timing issue when both R16 low mobility and R17 stationary criteria are configured for a UE | Futurewei Technologies |
| R2-2201239 | RRM relaxation in RRC_CONNECTED for RedCap UEs | Sharp |
| R2-2201337 | Open issues on RRM relaxations | DENSO CORPORATION |
| R2-2201493 | On RRM relaxations for REDCAP | Nokia, Nokia Shanghai Bell |
| R2-2201494 | On RRM relaxations in CONNECTED | Nokia, Nokia Shanghai Bell |
| R2-2201558 | Details on RRM relaxation | Ericsson |
| R2-2201735 | Report of [AT116bis-e][104][RedCap] RRM relaxations (Samsung) | Samsung |
| R2-2201752 | Report of [AT116bis-e][104][RedCap] RRM relaxations – 2nd round | Samsung |
| R2-2201854 | Report of [AT116bis-e][104][RedCap] RRM relaxations (Samsung) | Samsung |
| 8.13.1 | Organizational | |
| R2-2200004 | Running 38.331 for introducing R17 SON | Ericsson |
| R2-2200010 | Running 38.331 for introducing R17 MDT | Huawei, HiSilicon |
| R2-2200053 | Running CR for TS 38.314 | CMCC |
| R2-2200054 | Report of [Post116-e][879][SON/MDT] Running R17 38.314 | CMCC |
| R2-2200056 | 37.320 Running CR for R17 MDT in NR and E-UTRAN | CMCC |
| R2-2200097 | LS on UP measurements for Successful Handover Report (R3-212935; contact: Ericsson) | RAN3 |
| R2-2200098 | Reply LS on UE context keeping in the source cell (R3-212944; contact: Ericsson) | RAN3 |
| R2-2200099 | LS Reply on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions (R3-214429; contact: Ericsson) | RAN3 |
| R2-2200103 | LS on NR-U channel information and procedures (R3-216042; contact: Samsung) | RAN3 |
| R2-2200105 | Reply LS on scenarios need to be supported for MRO in SCG Failure Report (R3-216159; contact: Samsung) | RAN3 |
| R2-2200156 | Reply LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions (S5-213499; contact: Ericsson) | SA5 |
| R2-2200157 | Reply LS on Report Amount for M4, M5, M6, M7 measurements (S5-214523; contact: Nokia) | SA5 |
| R2-2200158 | Reply LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions (S5-215493; contact: Ericsson) | SA5 |
| R2-2200163 | Reply LS on the Beam measurement reports for the MDT measurements (S5-216628; contact: Ericsson) | SA5 |
| R2-2200664 | [Draft] Reply LS on NR-U channel information and procedures | Samsung |
| R2-2201611 | LS Reply on user plane masurements for successful handover report | Ericsson |
| R2-2201691 | Summary on issues for MDT RRC CR | Huawei, HiSilicon |
| R2-2201923 | Reply LS on NR-U channel information and procedures | RAN2 |
| R2-2201959 | Reply LS on NR-U channel information and procedures | RAN2 |
| R2-2202015 | MDT Stage 2 open issues list | Nokia (Rapporteur) |
| 8.13.2 | SON | |
| R2-2201680 | Summary of AI 8.13.2 on SON open issues (Ericsson)_v00 | Ericsson |
| R2-2201991 | SON related open issue list (Ericsson) | Ericsson |
| 8.13.2.1 | Handover related SON aspects | |
| R2-2200005 | Report of [Post116-e][887.5][SONMDT] Leftover issues on SON (Ericsson) | Ericsson |
| R2-2200392 | Further Discussion on Handover Related SON Aspects | CATT |
| R2-2200560 | Further consideration of SON of HO related aspects | OPPO |
| R2-2200561 | Further consideration on successful handover report | OPPO |
| R2-2200575 | Remaining issues on SHR | NEC |
| R2-2200668 | SON Enhancements for CHO Optimization | Samsung |
| R2-2200669 | SON Enhancements for Successful HO Report | Samsung |
| R2-2200752 | SON Enhancements for CHO | Lenovo, Motorola Mobility |
| R2-2200753 | SON Enhancements for SHR | Lenovo, Motorola Mobility |
| R2-2200901 | On measurements of CHO candidate cells | CMCC, Ericsson, Huawei, Nokia, ZTE |
| R2-2200902 | Remaining issues on SON Enhancement for CHO | CMCC |
| R2-2200903 | Further Discussion on Successful Handover Report | CMCC |
| R2-2200966 | Discussion on handover related SON aspects | Huawei, HiSilicon |
| R2-2201035 | HO related SON changes | Qualcomm Incorporated |
| R2-2201036 | Open Issues in Successful Handover Report | Qualcomm Incorporated |
| R2-2201211 | Remaining CHO related issues on SON | LG Electronics |
| R2-2201212 | Remaining SHR related issues on SON | LG Electronics |
| R2-2201229 | Successful HO report in CHO recovery case | SHARP Corporation |
| R2-2201230 | Discussion on successful HO report in DC case | SHARP Corporation |
| R2-2201326 | Further consideration on SHR enhancements | ZTE Corporation, Sanechips |
| R2-2201423 | Discussion on SHR enhancements | vivo |
| R2-2201612 | Handover-related SON aspects | Ericsson |
| 8.13.2.2 | 2-step RA related SON aspects | |
| R2-2200393 | The left issues on 2-step RA Report | CATT |
| R2-2200670 | 2-step Random Access Optimization | Samsung |
| R2-2200900 | Remaining issues for 2-step RA | CMCC,ZTE |
| R2-2200967 | Discussion on 2 step RA related SON aspects | Huawei, HiSilicon |
| R2-2201327 | Remaining issues on RA-report enhancements | ZTE Corporation, Sanechips |
| R2-2201604 | 2-Step RA information for SON purposes | Ericsson |
| 8.13.2.3 | Other WID related SON features | |
| R2-2200394 | Specification Impact of SgNB RACH Report on TS38.331 and TS36.331 | CATT |
| R2-2200395 | Open Issues of PSCell MHI Enhancement | CATT |
| R2-2200679 | SON Enhancements: Others | Samsung |
| R2-2200968 | Discussion on UE capabilities for R17 SON and MDT | Huawei, HiSilicon |
| R2-2201037 | Open Issues in Other SON Topics | Qualcomm Incorporated |
| R2-2201043 | Mobility History Information storing | Nokia, Nokia Shanghai Bell |
| R2-2201044 | Discussion on other SON features | Nokia, Nokia Shanghai Bell |
| R2-2201045 | Reporting Enhancements for SON in unlicensed | Nokia, Nokia Shanghai Bell |
| R2-2201213 | Remaining issues on SCG related MRO | LG Electronics |
| R2-2201328 | Consideration on SN MHI enhancements | ZTE Corporation, Sanechips |
| R2-2201329 | Clarification on failureType of SCG failure information | ZTE Corporation, Sanechips, CMCC |
| R2-2201605 | On Other WID related SON features | Ericsson |
| 8.13.3 | MDT | |
| R2-2201658 | Summary of AI 8.13.3 MDT aspects | ZTE Corporation, Sanechips |
| R2-2201927 | Summary of [At116bis-e][offline 877] MDT aspects | ZTE Corporation, Sanechips |
| R2-2201986 | Summary on MDT related open issue list | Huawei |
| 8.13.3.1 | Immediate MDT enhancements | |
| R2-2200396 | The Corrections on Immediate MDT Enhancements | CATT |
| R2-2200890 | On Immediate MDT Enhancements | Ericsson |
| R2-2200969 | Discussion on immediate MDT enhancements | Huawei, HiSilicon |
| R2-2201330 | Consideration on miscellaneous on IMM MDT | ZTE Corporation, Sanechips |
| 8.13.3.2 | Logged MDT enhancements | |
| R2-2200397 | Discussion on Logged MDT Enhancement | CATT |
| R2-2200648 | Discussion on multiple CEF reports | Samsung Electronics Co., Ltd |
| R2-2200680 | SI Request Optimization | Samsung |
| R2-2200889 | On logged MDT related enhancements | Ericsson |
| R2-2200970 | Discussion on logged MDT enhancements | Huawei, HiSilicon |
| R2-2201038 | Logged measurement Enhancements | Qualcomm Incorporated |
| R2-2201042 | Remaining Stage 2 open issues | Nokia, Nokia Shanghai Bell, CMCC |
| R2-2201331 | Remaining issues on logged MDT enhancements | ZTE Corporation, Sanechips |
| 8.13.4 | L2 Measurements | |
| R2-2200888 | On layer-2 measurements | Ericsson |
| R2-2200971 | Discussion on L2M | Huawei, HiSilicon |
| 8.14 | NR QoE | |
| R2-2201878 | RAN visible QoE | Qualcomm Incorporated |
| 8.14.1 | Organizational | |
| R2-2200109 | LS on the support of including slice ID in the QoE reporting container (R3-216225; contact: Huawei) | RAN3 |
| R2-2200152 | Reply LS on QoE report handling at QoE pause (S3-214458; contact: Lenovo) | SA3 |
| R2-2200160 | LS on the mapping between service types and slice at application (S5-216414; contact: Ericsson) | SA5 |
| R2-2200161 | LS on QoE configuration and reporting related issues (S5-216415; contact: Ericsson) | SA5 |
| R2-2200162 | LS Reply on QoE report handling at QoE pause (S5-216417; contact: Ericsson) | SA5 |
| R2-2200996 | Running RRC CR for QoE measurements | Ericsson |
| R2-2202019 | Running CR for Introduction of QoE measurements in NR | Ericsson |
| R2-2202043 | QoE related open issue list (China Unicom) | China Unicom |
| 8.14.2 | RAN Visible QoE | |
| R2-2200110 | RAN3 agreements on RAN visible QoE (R3-216227; contact: Qualcomm) | RAN3 |
| R2-2200268 | Discussion on RAN Visible QoE | ZTE Corporation, Sanechips |
| R2-2200546 | RAN visible QoE configuration and report | Samsung |
| R2-2200558 | Discussion on RAN visible QoE configuration | OPPO |
| R2-2200705 | Support of RAN visible QoE and per-slice QoE | Qualcomm Incorporated |
| R2-2200822 | RAN visible QoE | Huawei, HiSilicon |
| R2-2200854 | Discussion on Ran visiable QoE | CMCC |
| R2-2200998 | RAN Visible QoE measurements | Ericsson |
| R2-2201047 | RAN visible QoE | Nokia, Nokia Shanghai Bell |
| R2-2201419 | Discussion on NR RAN-visible QoE | CATT |
| R2-2201594 | Discussion on RAN visible QoE measurement in Rel-17 | China Unicom |
| R2-2201596 | Discussion on RAN Visible QoE | vivo |
| R2-2201626 | Discussion on RV QoE | LG Electronics |
| R2-2202026 | Reply LS on RAN visible QoE | RAN2 |
| 8.14.3 | Open Issues | |
| R2-2200011 | Summary of e-mail discussion [080] Mobility | Ericsson |
| R2-2200059 | Summary of e-mail discussion [080] Mobility | Ericsson |
| R2-2200266 | Discussion on NR QoE Pause Resume Reporting | ZTE Corporation, Sanechips |
| R2-2200267 | Discussion on QoE configuration | ZTE Corporation, Sanechips |
| R2-2200340 | Discussion on the partial QoE reporting at RAN overload | ITRI |
| R2-2200548 | Remaining QoE issues | Samsung |
| R2-2200557 | Discussion on QoE measurement collection configuration in NR | OPPO |
| R2-2200684 | Leftover issues of QoE configuration, reporting, pause, resume and mobility | Qualcomm Incorporated |
| R2-2200820 | Discussion on QoE open issues | Huawei, HiSilicon |
| R2-2200823 | [DRAFT] Further reply on QoE report handling at QoE pause | Huawei, HiSilicon |
| R2-2200824 | Draft reply LS on QoE configuration and reporting related issues | Huawei, HiSilicon |
| R2-2200851 | Remaining open issues on QoE measurement and mobility | CMCC |
| R2-2200997 | Configuration and reporting of QoE measurements | Ericsson |
| R2-2200999 | Pause and resume of QoE measurement reporting | Ericsson |
| R2-2201046 | Discussion on open issues for QoE | Nokia, Nokia Shanghai Bell |
| R2-2201183 | Supporting session continuity for NR QoE | Apple |
| R2-2201293 | QoE pause and resume | LG Electronics |
| R2-2201421 | Discussion on the remaining open issues | CATT |
| R2-2201593 | Discussion on pause and resume in NR QoE in Rel-17 | China Unicom, CMCC, ZTE, CATT, Nokia, Nokia Shanghai Bell |
| R2-2201595 | Discussion on Pause and Resume | vivo |
| R2-2201839 | Summary of e-mail discussion [080] Mobility | Ericsson |
| R2-2201862 | Further reply on QoE report handling at QoE pause | RAN2 |
| R2-2201919 | Feature summary for 8.14.3 | Ericsson |
| R2-2201926 | Feature summary for 8.14.3 | Ericsson |
| R2-2202017 | LS on the specification of AT commands for NR QoE | RAN2 |
| R2-2202018 | Reply LS on maximum container size for QoE configuration and report | RAN2 |
| 8.14.4 | UE capabilities | |
| R2-2200547 | RRC segmentation for QoE reports | Samsung |
| R2-2200707 | UE capability for QoE | Qualcomm Incorporated |
| R2-2200821 | Discussion on UE capabilities for NR QoE | Huawei, HiSilicon |
| R2-2200852 | Discussion on UE capability for NR QoE | CMCC, China Unicom |
| R2-2200853 | Running CR of UE capability for NR QoE | CMCC, China Unicom |
| R2-2201048 | UE capabilities for QoE | Nokia, Nokia Shanghai Bell |
| R2-2201420 | Discussion on UE capabilities for NR QoE | CATT |
| R2-2201855 | Report of [AT116bis-e][031][QoE] UE capabilities (CMCC) | CMCC |
| R2-2201856 | Running CR of UE capability for NR QoE | CMCC, China Unicom |
| 8.15.1 | Organizational | |
| R2-2200265 | Running CR of TS 38.304 for eSL | ZTE Corporation, Sanechips |
| R2-2200482 | RRC running CR for NR Sidelink enhancements | Huawei, HiSilicon |
| R2-2200550 | Running CR of TS 38.321 for Sidelink enhancement | LG Electronics France |
| R2-2201801 | Running CR of TS 38.304 for eSL | ZTE Corporation, Sanechips |
| R2-2201802 | RRC running CR for NR Sidelink enhancements | Huawei, HiSilicon |
| R2-2201803 | Running CR of TS 38.321 for Sidelink enhancement | LG Electronics France |
| R2-2201808 | Stage 2 Running CR of TS 38.300 for eSL | InterDigital |
| 8.15.2 | SL DRX | |
| R2-2200007 | Summary of [POST116-e][718][V2X SL] SL DRX configuration (Ericsson) | Ericsson |
| R2-2200045 | Summary of [POST116-e][715][V2X/SL] RRC open issues | Huawei, HiSilicon (Rapporteur) |
| R2-2200051 | Summary of [POST116-e][716][SL] MAC open issues | LG Electronics Inc. (Rapporteur) |
| R2-2200264 | Discussion on remaining issues of SL DRX | ZTE Corporation, Sanechips |
| R2-2200318 | Leftover Issues for Sidelink Unicast DRX | CATT |
| R2-2200319 | Leftover issues for Sidelink GCBC DRX | CATT |
| R2-2200344 | Further discussions on leftover issues of sidelink DRX configuration | NEC Corporation |
| R2-2200345 | Further discussions on sidelink MAC open issues | NEC Corporation |
| R2-2200373 | Discussion on DRX left issues | OPPO |
| R2-2200374 | Discussion on DRX left issues from [716] [718] | OPPO |
| R2-2200415 | SL DRX CP aspects | Lenovo, Motorola Mobility |
| R2-2200483 | Remaining issues for sidelink DRX | Huawei, HiSilicon |
| R2-2200484 | Remaining issues of SL communication impact on Uu DRX | Huawei, HiSilicon |
| R2-2200528 | Leftover aspects on SL DRX | Intel Corporation |
| R2-2200530 | On SL DRX and candidate resource selection | Intel Corporation |
| R2-2200535 | Discussion on remaining issues for SL DRX | LG Electronics France |
| R2-2200536 | Consideration on sidelink DRX for unicast | LG Electronics France |
| R2-2200544 | Consideration on sidelink DRX for unicast | LG Electronics France |
| R2-2200545 | Discussion on resource (re-)selection in SL DRX | SHARP Corporation |
| R2-2200749 | Discussion on remaining issues regarding Sidelink DRX | ASUSTeK |
| R2-2200762 | Remaining MAC issues for SL DRX | Lenovo, Motorola Mobility |
| R2-2200786 | NR Sidelink Synchronization Reference Search Optimization at UE for Power Saving | Nokia, Nokia Shanghai Bell |
| R2-2200790 | Discussion on Uu impact | Xiaomi |
| R2-2200791 | Discussion on Sidelink DRX open issues | Xiaomi |
| R2-2200893 | RRC remaining issues on SL DRX | vivo |
| R2-2200894 | MAC remaining issues on SL DRX | vivo |
| R2-2200938 | Remaining aspects of SL DRX | Ericsson |
| R2-2201061 | Discussion on remaining issues of SL DRX timers | ZTE Corporation, Sanechips |
| R2-2201135 | Discussion on remaining issues on SL-DRX | Apple |
| R2-2201150 | Resource Selection Considering DRX | InterDigital |
| R2-2201151 | Consideration of the Active Time for Periodic Transmissions | InterDigital, Ericsson, ZTE, AsusTek, Huawei, HiSilicon, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell |
| R2-2201152 | Remaining Aspects on SL DRX | InterDigital |
| R2-2201458 | SL data transmission considering SL DRX active time | Nokia, Nokia Shanghai Bell |
| R2-2201478 | Resource selection considering SL DRX | ITL |
| R2-2201523 | SL DRX CP aspects | Lenovo, Motorola Mobility |
| R2-2201582 | UE report on SL DRX for Uu DRX alignment | Samsung Research America |
| R2-2201585 | Remaining details for GC/BC | Samsung Research America |
| R2-2201624 | Discussion on Remaining Design Aspects for SL DRX | Qualcomm Finland RFFE Oy |
| R2-2201635 | Consideration of the Active Time for Periodic Transmissions | InterDigital Inc., Ericsson, ZTE, AsusTek, Huawei, HiSilicon, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Samsung |
| R2-2201805 | Summary of [705] | OPPO |
| 8.15.3 | Resource allocation enhancements RAN2 scope | |
| R2-2200263 | Discussion on inter-UE coordination | ZTE Corporation, Sanechips |
| R2-2200317 | Consideration on Resource Allocation Enhancements | CATT |
| R2-2200349 | Discussion on candidate resource selection with DRX and inter-UE coordination | NEC Corporation |
| R2-2200375 | Discussion on resource allocation enhancement | OPPO |
| R2-2200379 | RAN2 aspects on resource allocation enhancements for Rel-17 eSL | vivo |
| R2-2200485 | Consideration on resource allocation enhancement | Huawei, HiSilicon |
| R2-2200529 | On resource allocation and inter-UE coordination | Intel Corporation |
| R2-2200537 | Discussion on Inter-UE Coondination MAC CE | LG Electronics France |
| R2-2200642 | Discussion on resource allocation enhancement for NR sidelink | Spreadtrum Communications |
| R2-2200750 | Discussion on inter-UE coordination | ASUSTeK |
| R2-2200763 | RAN2 impacts on SL Resource allocation enhancements | Lenovo, Motorola Mobility |
| R2-2200792 | Discussion on inter-UE coordination impact in RAN2 | Xiaomi |
| R2-2200799 | On Signalling for Inter UE Coordination | Nokia, Nokia Shanghai Bell |
| R2-2200939 | MAC CE design of inter-UE coordination | Ericsson |
| R2-2201134 | Discussion on Inter-UE Coordination | Apple |
| R2-2201457 | Power Reduction for Sidelink Mode 2 Resource Allocation | Fraunhofer IIS, Fraunhofer HHI |
| R2-2201459 | Inter-UE Coordination for Sidelink Mode 2 Resource Allocation | Fraunhofer IIS, Fraunhofer HHI |
| R2-2201479 | Interaction between partial sensing and DRX | Ericsson |
| R2-2201591 | Resource allocation enhancements | Samsung Research America |
| R2-2201625 | Discussion on Inter-UE Coordination | Qualcomm Finland RFFE Oy |
| R2-2201804 | Summary of [AT116bis-e][704][V2X/SL] Resource allocation enhancements | LG Electronics Inc. (Rapporteur) |
| R2-2201806 | Summary of [POST116bis-e][706][V2X/SL] Open issues on power-saving resource allocation, Phase 1 | vivo |
| R2-2201807 | Summary of [POST116bis-e][707][V2X/SL] Open issues on IUC, Phase 1 | LG |
| R2-2201809 | LS to RAN1 on Inter-UE coordination | RAN2 |
| 8.16.1 | Organizational | |
| R2-2200138 | Reply to LS on support of PWS over SNPN (S1-214049; contact: Nokia) | SA1 |
| R2-2200143 | Reply LS on limited service availability of an SNPN (S2-2109254; contact: Qualcomm) | SA2 |
| R2-2200491 | Draft CR for Enhancements for Private Networks | Qualcomm Incorporated |
| 8.16.2 | Issues and Corrections | |
| R2-2201470 | Details of SIBxy | LG Electronics |
| 8.16.3 | UE capabilities | |
| R2-2200233 | UE Capabilities for eNPN | OPPO |
| R2-2200293 | Discussion on UE capability for eNPN | Huawei, HiSilicon |
| R2-2200508 | UE capability for Rel-17 NPN | Intel Corporation, Nokia, Nokia Shanghai Bell |
| R2-2200509 | UE capability for Rel-17 NPN | Intel Corporation, Nokia, Nokia Shanghai Bell |
| R2-2200521 | Discussion of UE capability of eNPN | China Telecom |
| R2-2200849 | Discussion on UE capability for NPN | CMCC |
| R2-2201236 | Consideration on the eNPN UE Capability | ZTE Corporation, Sanechips |
| R2-2201266 | Discussion on UE capabilities for R17 NPN | vivo |
| R2-2201469 | UE capabilities | LG Electronics |
| R2-2201524 | Discussion on UE capabilities relating to Rel17 eNPN features | Samsung R&D Institute India |
| R2-2201566 | UE capabilities for eNPN | Ericsson |
| R2-2201909 | Report of Offline on Rel-17 NPN UE capability for Rel-17 NPN | Intel Corporation |
| 8.17.1 | Organizational | |
| R2-2200067 | Follow-up reply LS on inter-cell beam management and multi-TRP in Rel-17 (R1-2112707; contact: Huawei) | RAN1 |
| R2-2200069 | LS on L1-RSRP measurement behaviour when SSBs associated with different PCIs overlap (R1-2112762; contact: vivo) | RAN1 |
| R2-2200077 | LS on BFR for CORESET with two activated TCI states (R1-2112829; ZTE) | RAN1 |
| R2-2200112 | Reply LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN3 (R3-216234; contact: ZTE) | RAN3 |
| R2-2200660 | MAC Running CR for Rel-17 feMIMO | Samsung |
| R2-2201560 | Running RRC CR for FeMIMO Rel-17 | Ericsson |
| R2-2201994 | MAC Running CR for Rel-17 feMIMO | Samsung |
| R2-2202000 | Running RRC CR for FeMIMO Rel-17 | Ericsson |
| R2-2202055 | FeMIMO L1 parameters with RAN2 notes Rel-17 NR Post 116bis | Ericsson |
| 8.17.2 | General and RRC | |
| R2-2200015 | Report of [Post116-e][086][feMIMO] RRC (Ericsson) | Ericsson |
| R2-2200016 | Running RRC CR for FeMIMO Rel-17 | Ericsson |
| R2-2200224 | RRC parameters for feMIMO | Intel Corporation |
| R2-2200260 | Implementation of MIMO RRC parameters | OPPO |
| R2-2200316 | Unified TCI Framework Operation from RAN2 Perspectives | MediaTek Inc. |
| R2-2200569 | Systerm Information provisioning for inter-cell beam management | Fujitsu |
| R2-2200599 | Discussion on RRC aspects for feMIMO | vivo |
| R2-2200635 | Discussion on inter-cell beam management | Spreadtrum Communications |
| R2-2200661 | RRC impacts for feMIMO | Samsung |
| R2-2200700 | Configuration and procedures for ICBM and mTRP | Qualcomm Incorporated |
| R2-2201058 | Discussion on MPE and mTRP | Nokia, Nokia Shanghai Bell |
| R2-2201098 | Inter-cell BM and inter-cell mTRP | Huawei, HiSilicon |
| R2-2201099 | FeMIMO RRC Discussion | Huawei, HiSilicon |
| R2-2201122 | RRC impact of FeMIMO | Apple |
| R2-2201223 | Considerations on Implementation Of Unified TCI Framework in RRC | ZTE Corporation,Sanechips |
| R2-2201253 | Discussion on the unified TCI framework | CATT |
| R2-2201254 | Considerations on Inter-cell Beam Management | CATT |
| R2-2201275 | Considerations on SI aspects of inter-cell beam management | NTT DOCOMO, INC. |
| R2-2201386 | Clarification on the serving cell measurement for mTRP | Xiaomi Communications |
| R2-2201466 | TCI state configuration for inter-cell BM | LG Electronics |
| R2-2201467 | Power control and miscellaneous parameters for inter-cell BM | LG Electronics |
| R2-2201581 | FeMIMO General and RRC impact | Ericsson |
| R2-2201719 | Report of [AT116bis-e][059][feMIMO] Specific items: SI, MPE (Nokia) | Nokia, Nokia Shanghai Bell |
| R2-2201921 | Report for [AT116bis-e][052][feMIMO] RRC progress (Ericsson) | Ericsson |
| R2-2202001 | feMIMO RRC open issues towards RAN2#117 | Ericsson |
| R2-2202002 | LS on feMIMO RRC parameters | RAN2 |
| 8.17.3 | Other | |
| R2-2200205 | Multi TRP Beam Failure Detection and Recovery | Samsung Electronics Co., Ltd |
| R2-2200225 | Remaining issues on HST-SFN PDCCH | Intel Corporation |
| R2-2200403 | Further discussions on BFD and BFR of mTRP | NEC Corporation |
| R2-2200404 | Further discussions on BFD and BFR of Unified TCI state and CA | NEC Corporation |
| R2-2200570 | RAN2 impacts of beam failure detection and recovery | Fujitsu |
| R2-2200600 | Discussion on BFD/BFR for mTRP | vivo |
| R2-2200662 | MAC CE impacts for feMIMO | Samsung |
| R2-2200719 | Remaining issues on multi-TRP BFR | Qualcomm Incorporated |
| R2-2200721 | PDCCH repetition impact on MAC and MIMO MAC CEs | Qualcomm Incorporated |
| R2-2200751 | Discussion on Power Headroom Reporting for mTRP PUSCH repetition | ASUSTeK |
| R2-2200755 | BFR for both SpCell and SCell in mTRP | Lenovo, Motorola Mobility |
| R2-2200782 | Discussion on MAC CEs for FeMIMO | OPPO |
| R2-2200783 | open issues on TRP-specific BFR | OPPO |
| R2-2201100 | FeMIMO MAC Discussion | Huawei, HiSilicon |
| R2-2201123 | MAC impact of FeMIMO | Apple |
| R2-2201168 | Discussion on Multi-TRP PHR enhancements | InterDigital |
| R2-2201224 | Consideration on Implementation of BFR For mTRP | ZTE Corporation,Sanechips |
| R2-2201225 | Initial Discussion on new PHR and new PHR MAC CE | ZTE Corporation,Sanechips |
| R2-2201255 | Remaining MAC Aspects for M-TRP | CATT |
| R2-2201359 | Remaining issues on BFD/BFR for mTRP | LG Electronics Inc. |
| R2-2201387 | Remaining issues of mTRP BFR | Xiaomi Communications |
| R2-2201464 | RAN2 aspects for BFR, BFD and RLM for mTRP operation | Ericsson |
| R2-2201529 | MAC CE impacts | Ericsson |
| R2-2201588 | Beam failure with mTRP | Nokia, Nokia Shanghai Bell |
| R2-2201694 | [Pre116bis] [010] [feMIMO] Summary of 8.17.3 Other (Samsung) | Samsung |
| R2-2201699 | [Pre116bis] [010] [feMIMO] Summary of 8.17.3 Other (Samsung) | Samsung |
| R2-2201949 | Summary of [AT116bis-e][060][feMIMO] MAC general (Samsung) | Samsung |
| R2-2201950 | [DRAFT] LS on Enhanced TCI state indication for UE-specific PDCCH MAC CE | Samsung |
| R2-2201995 | LS on Enhanced TCI state indication for UE-specific PDCCH MAC CE | RAN2 |
| 8.18 | RACH indication and partitioning | |
| R2-2202046 | Open issue list for 38.331 for RIP | Ericsson |
| 8.18.1 | Common signalling framework | |
| R2-2200019 | Running CR to 38.331 on RA Partitioning | Ericsson |
| R2-2200020 | [Post116-e][514][RACH partitioning] Signaling design (Ericsson) | Email discussion Rapporteur (Ericsson) |
| R2-2200206 | Preamble and RACH resource configuration | Samsung Electronics Co., Ltd |
| R2-2200261 | RRC aspects of RACH partition | OPPO |
| R2-2200419 | Discussion on signaling design for RACH partitioning | CATT |
| R2-2200456 | Signalling design of RACH partitioning for multiple feature combinations | Intel Corporation |
| R2-2200701 | Consideration on the common signalling framework for RACH partitioning | Beijing Xiaomi Software Tech |
| R2-2200812 | Common signalling for RACH indication and partitioning | Huawei, HiSilicon |
| R2-2201049 | Features Combination signalling | Nokia, Nokia Shanghai Bell |
| R2-2201127 | Signaling aspects of RACH partitioning | Apple |
| R2-2201128 | MAC aspects of RACH partitioning | Apple |
| R2-2201473 | Discussion on signalling aspects on common RACH framework | LG Electronics Inc. |
| R2-2201553 | RACH partitioning for Rel-17 features | Ericsson |
| R2-2201597 | Discussion on RACH Partitioning in RA Configuration Aspect | vivo |
| R2-2202045 | Running CR to 38.331 on RA Partitioning | Ericsson |
| 8.18.2 | Common aspects of RACH procedure | |
| R2-2200049 | [Post116-e][515][RACH partitioning] MAC Procedure aspects (ZTE) | email discussion Rapporteur (ZTE Corporation) |
| R2-2200193 | Selection and fallback between RACH partitions | Qualcomm Incorporated |
| R2-2200207 | RA Procedure Aspects | Samsung Electronics Co., Ltd |
| R2-2200262 | MAC aspects of RACH partition | OPPO |
| R2-2200420 | Discussion on MAC procedure for RACH partitioning | CATT |
| R2-2200457 | RACH resource/configuration selection and fallback mechanism | Intel Corporation |
| R2-2200617 | Remaining issues for MAC procedure in RACH partition | NEC |
| R2-2200703 | Considerations on the common aspects of RACH procedure | Beijing Xiaomi Software Tech |
| R2-2200813 | MAC aspects for RACH partitioning | Huawei, HiSilicon |
| R2-2200848 | Discussion on RACH indication and partitioning | CMCC |
| R2-2200917 | RNTI collision issue for different features in NR | Sony |
| R2-2201025 | RACH indication and partitioning | InterDigital |
| R2-2201026 | Updated - [Post116-e][515][RACH partitioning] MAC Procedure aspects (ZTE) | email discussion Rapporteur (ZTE Corporation) |
| R2-2201031 | MAC procedure aspects of RACH partitioning | ZTE corporation, Sanechips |
| R2-2201474 | Further discussion on common RA procedure | LG Electronics Inc. |
| R2-2201554 | RNTI collision problem for Rel-17 features | Ericsson |
| R2-2201589 | Selection of RACH partition | Nokia, Nokia Shanghai Bell |
| R2-2201628 | Discussion on RACH Partitioning in RA Procedure Aspect | vivo |
| R2-2202023 | Introduction of common RACH partitioning aspects | ZTE Corporation (rapporteur) |
| R2-2202024 | UP open issues list for common RACH (email: [POST116bis-e][514]) | ZTE Corporation (rapporteur) |
| 8.19.1 | Organizational | |
| R2-2200515 | Running 38300 CR for NR coverage enhancements | China Telecom |
| R2-2200602 | Running 38321 CR for NR coverage enhancements | ZTE Corporation |
| R2-2201616 | RRC running CR for CE | Huawei, HiSilicon |
| R2-2201784 | LS on Stage 2 description for Coverage Enhancements | RAN2 |
| R2-2201963 | Running 38300 CR for NR coverage enhancements | China Telecom |
| R2-2201964 | RRC running CR for CE | Huawei, HiSilicon |
| R2-2201966 | Running 38321 CR for NR coverage enhancements | ZTE Corporation |
| 8.19.2 | General | |
| R2-2200192 | Issues on coverage enhancements | Qualcomm Incorporated |
| R2-2200251 | Discussion on CE’s impact on UL carrier selection | OPPO |
| R2-2200269 | Considerations on requesting Msg3 repetition | NEC Corporation |
| R2-2200272 | Remaining issues related to coverage enhancement | Xiaomi |
| R2-2200421 | Consideration on RAN2 impacts of Msg3 repetition | CATT |
| R2-2200603 | Remaining issues on Msg3 repetition in CE | ZTE Corporation, Sanechips |
| R2-2201177 | Further Discussion on RAN2 Impacts of Msg3 Repetition | vivo |
| R2-2201426 | Remaining issues for supporting Msg3 repetition | LG Electronics Inc. |
| R2-2201590 | RAN2 aspects for Coverage Enhancement | Nokia, Nokia Shanghai Bell |
| R2-2201598 | On Type A PUSCH repetitions for Msg3 | Ericsson |
| R2-2201617 | Remaining issues on RAN2 support of Msg3 PUSCH repetition | Huawei, HiSilicon |
| R2-2201747 | Report of [AT116bis-e][111][CovEnh] General aspects | Qualcomm Incorporated |
| R2-2201758 | Report for [AT116bis-e][111][CovEnh] General aspects | Qualcomm Incorporated |
| R2-2201882 | LS on BWP with only CE RACH resources | Qualcomm |
| R2-2201982 | LS on UL BWP with PRACH resources only for RACH with Msg3 repetition | RAN2 |
| 8.20.1 | Organizational | |
| R2-2200006 | Extending NR operation to 71 GHz | Ericsson |
| R2-2200017 | Running CR to 38306 for NR operation for up to 71G | Intel Corporation |
| R2-2200018 | Running CR to 38331 on UE capability for 71G | Intel Corporation |
| R2-2200076 | LS on initial access for 60 GHz (R1-2112805; contact: Intel) | RAN1 |
| R2-2200078 | LS on RA-RNTI and MSGB-RNTI for 480 and 960 kHz (R1-2112832; contact: Intel) | RAN1 |
| R2-2200718 | List of issues for completion of FR2-2 Work (Rapporteur Input) | Qualcomm Incorporated |
| R2-2200720 | Running Stage-2 CR for Extending NR operation to 71GHz | Qualcomm Incorporated |
| R2-2200940 | Open issue list of RRC CR for 71 GHz | Ericsson (rapporteur) |
| R2-2201716 | Running Stage-2 CR for Extending NR operation to 71GHz | Qualcomm Incorporated |
| R2-2201720 | Reply LS on initial access for 60 GHz | RAN2 |
| R2-2201783 | Running CR to 38331 on UE capability for 71G | Intel Corporation |
| R2-2201948 | [DRAFT] Reply LS on initial access for 60 GHz | Intel Corporation |
| R2-2201975 | Extending NR operation to 71 GHz | Ericsson |
| R2-2202004 | Running CR to 38306 for NR operation for up to 71G | Intel Corporation |
| R2-2202058 | [Post116bis-e][204][71 GHz] Open issues for 71 GHz (Qualcomm) | Qualcomm Incorporated |
| 8.20.2 | General | |
| R2-2200274 | Consideration on support of directional LBT | Xiaomi |
| R2-2200460 | Remaining UE capability issues on NR operation for upto 71GHz | Intel Corporation |
| R2-2200461 | UP and CP impact on NR operation for upto 71GHz | Intel Corporation |
| R2-2200480 | Discussion about RAN2 impacts of Ext 52-71GHz | Huawei, HiSilicon |
| R2-2200481 | Discussion about UE capabilities of Ext 52-71GHz | Huawei, HiSilicon |
| R2-2200706 | Discussion on potential LBT impacts | Lenovo, Motorola Mobility |
| R2-2200732 | Discussion on L2 buffer size | Samsung |
| R2-2200733 | Discussion on UAI enhancement for operation in FR2-2 | Samsung |
| R2-2200884 | Initial access aspects | Nokia, Nokia Shanghai Bell |
| R2-2200885 | RA-RNTI | Nokia, Nokia Shanghai Bell |
| R2-2200941 | Remaining protocol aspects | Ericsson |
| R2-2200942 | Remaining RRC aspects | Ericsson |
| R2-2201014 | Impacts of directional LBT on MAC procedure | OPPO |
| R2-2201015 | On the issues of RA-RNTI and Initial Access | OPPO |
| R2-2201032 | Consideration on LBT impact | ZTE corporation, Sanechips |
| R2-2201033 | Consideration on RRC and MAC running CR | ZTE corporation, Sanechips |
| R2-2201284 | Remaining issues for Ext 71GHz | vivo Mobile Com. (Chongqing) |
| R2-2201424 | Discussion on RAN1 LS and L2 buffer size | LG Electronics Inc. |
| R2-2201425 | Discussion on LBT impact based on RAN1 conclusions | LG Electronics Inc. |
| R2-2201438 | Discussion on Consistent LBT Failure Detection for Ext 71GHz | vivo |
| R2-2201682 | Discussion about RAN2 impacts of Ext 52-71GHz | Huawei, HiSilicon |
| R2-2201683 | Discussion about UE capabilities of Ext 52-71GHz | Huawei, HiSilicon |
| R2-2201709 | Summary of [AT116bis-e][211][71 GHz] LBT aspects for 71 GHz (Lenovo) | Lenovo |
| R2-2201710 | Summary of [AT116bis-e][210][71 GHz] RRC aspects of CR for 71 GHz (Qualcomm) | Qualcomm |
| 8.21.1 | TEI proposals initiated by other groups | |
| R2-2200434 | Introduction of RACH triggers for T_ADV in NR E-CID [NRTADV] | Huawei, HiSilicon, Ericsson, CATT, NTT DOCOMO, Deutsche Telecom, Polaris Wireless, ZTE Corporation |
| 8.21.2 | TEI proposals initiated by RAN2 | |
| R2-2200046 | Report on Explicit SI start position for SI Scheduling | Ericsson |
| R2-2200423 | EPS Fallback | Lenovo, Motorola Mobility |
| R2-2200723 | Discussion on Secondary DRX Enhancement | LG Electronics Deutschland |
| R2-2201071 | Explicit Indication of SI Scheduling start position | Ericsson, Verizon, Softbank, Deutsche Telekom |
| R2-2201085 | System information scheduling enhancements for Rel-17 | MediaTek Inc. |
| R2-2201086 | Updating 80ms hardcoded offset with shortest configured SI-Periodicity offset for positioning SI Scheduling | MediaTek Inc., Ericsson, Verizon, Softbank, Apple, Deutsche Telekom |
| R2-2201130 | SDAP end-marker in RLC UM | Apple, Futurewei, Spreadtrum, FGI, Asia Pacific Telecom |
| R2-2201140 | Discussion on UE capability signaling of inactiveStatePO-Determination-r17 in LTE | Lenovo, Motorola Mobility |
| R2-2201320 | Discussion on EPS fallback enhancement | Apple |
| R2-2201392 | Discussion on SI Scheduling | vivo |
| R2-2201398 | Early measurement for EPS Fallback | vivo,CMCC, Softbank, China Telecom,China Unicom, Vodafone, Ericsson |
| R2-2201399 | 38331 CR for Early measurement for EPS Fallback | vivo,CMCC, Softbank, China Telecom,China Unicom, Vodafone |
| R2-2201400 | 38306 CR for Early measurement for EPS Fallback | vivo,CMCC, Softbank, China Telecom,China Unicom, Vodafone |
| R2-2201401 | Redirection enhancement on EPS Fallback | vivo |
| R2-2201402 | 38331 CR for Redirection enhancement on EPS Fallback | vivo |
| R2-2201403 | 38306 CR for Redirection enhancement on EPS Fallback | vivo |
| R2-2201472 | Configuration of chronological order for performing inter-frequency measurements | BT Plc., Ericsson, Vodafone, T-Mobile USA, Qualcomm |
| R2-2201498 | EPS fallback enhancements in Rel-17 | Huawei, HiSilicon, CMCC, China Telecom, China Unicom, LG Uplus |
| R2-2201518 | DRX HARQ RTT timer for one-shot HARQ feedback | LG Electronics |
| R2-2201519 | CR for DRX HARQ RTT Timer for one-shot HARQ-ACK | LG Electronics |
| R2-2201559 | Secondary DRX enhancement | Ericsson, Verizon, Qualcomm Inc, T-Mobile USA Inc., Deutsche Telekom |
| R2-2201676 | SDAP end-marker in RLC UM | Apple, Futurewei, Spreadtrum, FGI, Asia Pacific Telecom, T-Mobile USA |
| R2-2201685 | Discussion on EPS fallback enhancement | Apple, T-Mobile USA, ZTE |
| R2-2201700 | Explicit Indication of SI Scheduling start position | Ericsson, Verizon, Softbank, Deutsche Telekom, vivo |
| 8.22.1 | Organizational | |
| R2-2200125 | LS on R17 NR MG enhancements – Pre-configured MG (R4-2120302; contact: CATT, Intel) | RAN4 |
| R2-2200126 | LS on multiple concurrent MGs (R4-2120304; contact: Huawei) | RAN4 |
| R2-2200127 | LS on NCSG (R4-2120306; contact: Apple) | RAN4 |
| R2-2200835 | RRC signaling of measurement gap enhancements | Huawei, HiSilicon |
| R2-2201241 | Progress on MG enhancement WI | MediaTek Inc., Intel |
| R2-2201903 | RRC signaling for measurement gap enhancement | MediaTek Inc. |
| 8.22.2 | Pre-configured MG patterns | |
| R2-2200219 | Stage 3 detail for pre-configured gap | Intel Corporation |
| R2-2200222 | Draft running CR to 38331 for pre-configured measurement gap to support case 5 | Intel Corporation |
| R2-2200223 | Draft running CR to 38331 for pre-configured measurement gap to support case 4 and 5 | Intel Corporation |
| R2-2200492 | Discussion on Pre-configured MG | OPPO |
| R2-2200497 | Preconfigured measurement gap patterns | Samsung |
| R2-2200499 | Discussion on Pre-Configured MG | CATT |
| R2-2200585 | Discussion on per-configured measurement gap | vivo |
| R2-2200606 | Discussion on Pre-Configured MG | ZTE Corporation, Sanechips |
| R2-2200832 | Discussion on Pre-configured MG | Huawei, HiSilicon |
| R2-2201011 | Discussion on support of Pre-Configured Measurement Gap | Nokia, Nokia Shanghai Bell |
| R2-2201107 | RAN2 impact from Rel-17 Pre-MG | Apple |
| R2-2201247 | Discussion on pre-configured MG | MediaTek Inc. |
| R2-2201272 | Discussion on Pre-configured MG | Xiaomi Communications |
| R2-2201287 | Pre-configured measurement gap | LG Electronics |
| R2-2201288 | Draft LS on NW-Controlled activationdeactivation of pre-configured MG | LG Electronics |
| R2-2201567 | Pre-configured measurement gaps | Ericsson |
| R2-2201687 | Summary of 8.22.2 MGE: pre-configured measurement gap | Intel |
| R2-2201925 | [AT116bis-e][062][MGE] pre-configured measurement gap (Intel) | Intel Corporation |
| R2-2201932 | [AT116bis-e][062][MGE] pre-configured measurement gap (Intel) | Intel Corporation |
| R2-2202049 | [Post116bis-e][085][MGE] Open Issues (Intel) | Intel Corporation |
| R2-2202054 | [Post116bis-e][085][MGE] Open Issues (Intel) | Intel Corporation |
| 8.22.3 | Multiple concurrent and independent MG patterns | |
| R2-2200220 | Stage 3 detail for concurrent gap | Intel Corporation |
| R2-2200462 | Draft running CR to 38331 for concurrent measurement gap | Intel Corporation |
| R2-2200493 | Discussion on Concurrent MG | OPPO |
| R2-2200496 | Discussion on concurrent MG patterns | Samsung |
| R2-2200500 | Discussion on Concurrent MG | CATT |
| R2-2200586 | Discussion on multiple concurrent and independent MG patterns | vivo |
| R2-2200607 | Association configuration of concurrent measurement gap | ZTE Corporation, Sanechips |
| R2-2200833 | Discussion on Concurrent MG | Huawei, HiSilicon |
| R2-2201012 | Discussion on support of Concurrent Measurement Gap | Nokia, Nokia Shanghai Bell |
| R2-2201108 | Discussion on Rel-17 concurrent gap | Apple |
| R2-2201274 | Discussion on Concurrent MG | Xiaomi Communications |
| R2-2201283 | Discussion on concurrent gap | MediaTek Inc. |
| R2-2201286 | Concurrent measurement gap | LG Electronics |
| R2-2201310 | Inter-node signalling design on multiple concurrent gaps for MR-DC | DENSO CORPORATION |
| R2-2201568 | Concurrent measurement gaps | Ericsson |
| R2-2201672 | [Pre116bis][012][MGE] Summary of 8.22.3 Multiple concurrent and independent MG patterns (MediaTek) | MediaTek Inc. |
| 8.22.4 | Network Controlled Small Gap | |
| R2-2200494 | Discussion on NCSG | OPPO |
| R2-2200498 | On Network Controlled Small Gaps | Samsung |
| R2-2200501 | MGDiscussion on NCSG | CATT |
| R2-2200587 | Discussion on NCSG | vivo |
| R2-2200834 | Discussion on NCSG | Huawei, HiSilicon |
| R2-2201013 | Discussion on support of Network Controlled Small Gaps (NCSG) | Nokia, Nokia Shanghai Bell |
| R2-2201106 | RAN2 impact from Rel-17 NCSG | Apple, MediaTek Inc. |
| R2-2201569 | Network Controlled Small Gap | Ericsson |
| R2-2201678 | Summary of AI 8.22.4 Network Controlled Small Gap (Apple) | Apple |
| R2-2201934 | Summary of [AT116bis-e][061][MGE] LS out (Apple) | Apple |
| R2-2201935 | Reply LS to RAN4 on NCSG | RAN2 |
| 8.23.1 | Organizational | |
| R2-2201276 | Work plan for NR UDC | CATT |
| R2-2201277 | Introduction of the support for UDC in NR | CATT, CMCC, Huawei, HiSilicon, MediaTek, Ericsson, China Unicom, China Telecom, OPPO, ZTE, Samsung |
| R2-2201278 | Introduction of the support for UDC in NR | CATT, CMCC, Huawei, HiSilicon, MediaTek, Ericsson, China Unicom, China Telecom, OPPO, ZTE, Samsung |
| R2-2201279 | Introduction of the support for UDC in NR | CATT, CMCC, Huawei, HiSilicon, MediaTek, Ericsson, China Unicom, China Telecom, OPPO, ZTE, Samsung |
| R2-2201280 | Introduction of the support for UDC in NR | CATT, CMCC, Huawei, HiSilicon, MediaTek, Ericsson, China Unicom, China Telecom, OPPO, ZTE, Samsung |
| R2-2201281 | Introduction of the support for UDC in NR | CATT, CMCC, Huawei, HiSilicon, MediaTek, Ericsson, China Unicom, China Telecom, OPPO, Samsung, Apple, Nokia, Nokia Shanghai Bell |
| R2-2202035 | Introduction of the support for UDC in NR | CATT, CMCC, Huawei, HiSilicon, MediaTek, Ericsson, China Unicom, China Telecom, OPPO, Samsung, Apple, Nokia, Nokia Shanghai Bell |
| R2-2202036 | Introduction of the support for UDC in NR | CATT, CMCC, Huawei, HiSilicon, MediaTek, Ericsson, China Unicom, China Telecom, OPPO, Samsung, Apple, Nokia, Nokia Shanghai Bell |
| R2-2202037 | Introduction of the support for UDC in NR | CATT, CMCC, Huawei, HiSilicon, MediaTek, Ericsson, China Unicom, China Telecom, OPPO, Samsung, Apple, Nokia, Nokia Shanghai Bell |
| R2-2202038 | Introduction of the support for UDC in NR | CATT, CMCC, Huawei, HiSilicon, MediaTek, Ericsson, China Unicom, China Telecom, OPPO, Samsung, Apple, Nokia, Nokia Shanghai Bell |
| R2-2202039 | Introduction of the support for UDC in NR | CATT, CMCC, Huawei, HiSilicon, MediaTek, Ericsson, China Unicom, China Telecom, OPPO, Samsung, Apple, Nokia, Nokia Shanghai Bell |
| 8.23.2 | General | |
| R2-2200039 | Report of [Post116-e][088][UDC] UDC initial discussion (CATT)? | CATT |
| R2-2200495 | Limit UL data rate for UDC in UE capability | MediaTek Inc. |
| R2-2200581 | Issue on UDC continuation | Samsung Electronics Polska |
| R2-2200724 | Remaining issues on NR UDC | Qualcomm Incorporated |
| R2-2200932 | Consideration on NR UDC | OPPO |
| R2-2200977 | Discussion on UDC support in NR | Huawei, HiSilicon |
| R2-2201129 | Open topics on UDC functionality | Apple |
| R2-2201227 | Furhter Consideration on UDC in NR | ZTE Corporation,Sanechips |
| R2-2201282 | Clarifications on NR UDC applicable scenarios | CATT, CMCC |
| R2-2201361 | Discussion on remaining issues for UDC | LG Electronics |
| R2-2201650 | Discussion on remaining issues for UDC | LG Electronics, Ericsson |
| R2-2201914 | Report of [AT116bis-e][053][UDC] General (CATT) | CATT |
| R2-2202033 | LS on NR UDC for CU-CP/UP splitting scenario | RAN2 |
| R2-2202034 | Report of [Post116bis-e][053][UDC] CRs and LS out (CATT) | CATT |
| 8.24.1 | RAN4 led Items | |
| R2-2200086 | Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure (R1-2112858; contact: Huawei) | RAN1 |
| R2-2200117 | LS on DC location for >2CC (R4-2119965; contact: Qualcomm) | RAN4 |
| R2-2200118 | LS on release independence aspects of newly introduced FR2 CA BW Classes and CBM/IBM UE capability “both” (R4-2119966; contact: Nokia) | RAN4 |
| R2-2200120 | LS on UL-MIMO coherence for Rel-17 Tx switching (R4-2120039; contact: China Telecom) | RAN4 |
| R2-2200122 | LS on UL gap in FR2 RF enhancement (R4-2120058; contact: Apple) | RAN4 |
| R2-2200123 | LS on signalling for RRM enhancements for Rel-17 NR FR1 HST (R4-2120286; contact: CMCC) | RAN4 |
| R2-2200124 | LS on HO with PSCell from NR SA to EN-DC (R4-2120298; contact: MediaTek) | RAN4 |
| R2-2200133 | LS on interruption for PUCCH SCell activation in invalid TA case (R4-2120420; contact: MediaTek, CATT) | RAN4 |
| R2-2200306 | DC location reporting for more than 2 CCs | Qualcomm Incorporated |
| R2-2200516 | Running CR to TS 38.306 to support Tx switching enhancements | China Telecom, Huawei, HiSilicon, Apple, CATT |
| R2-2200517 | Draft CR to TS 38.306 on UE capability for UL-MIMO coherence for Rel-17 Tx switching | China Telecom, Huawei, HiSilicon |
| R2-2200518 | Draft CR to TS 38.331 on UE capability for UL-MIMO coherence for Rel-17 Tx switching | China Telecom, Huawei, HiSilicon |
| R2-2200519 | Discussion on UL MIMO coherence for UL Tx switching | China Telecom, Huawei, HiSilicon |
| R2-2200839 | Introduction of FR2 FBG2 CA BW classes | Nokia Italy |
| R2-2200840 | Introduction of CBM/IBM UE capability “both” | Nokia Italy |
| R2-2200841 | Introduction of CBM/IBM UE capability “both” | Nokia Italy |
| R2-2200843 | Reply LS on release independence aspects of newly introduced FR2 CA BW Classes and CBM/IBM UE capability | Nokia Italy |
| R2-2200864 | Introduction of RRM enhancements for Rel-17 NR FR1 HST | CMCC, Ericsson |
| R2-2200865 | Introduction of RRM enhancements for Rel-17 NR FR1 HST | CMCC, Ericsson |
| R2-2200891 | Discussion on interruption for PUCCH SCell activation in invalid TA case | CATT |
| R2-2200892 | [Draft] Reply LS on interruption for PUCCH SCell activation in invalid TA case | CATT |
| R2-2201059 | DC location for >2UL CCs | Nokia, Nokia Shanghai Bell |
| R2-2201105 | RAN2 impact from UL gap in FR2 RF enhancement | Apple |
| R2-2201334 | Discussion on the signaling for RRM enhancement for Rel-17 HST | Huawei, HiSilicon |
| R2-2201335 | On the signaling for RRM enhancements for Rel-17 HST | Huawei, HiSilicon |
| R2-2201336 | On the UE capabilities for RRM enhancements for Rel-17 HST | Huawei, HiSilicon |
| R2-2201341 | PUCCH SCell activation | Nokia, Nokia Shanghai Bell |
| R2-2201371 | Introduction of BCS4 and BCS5 | Xiaomi Communications, Samsung, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, OPPO, Huawei, HiSilicon, ZTE Corporation, Sanechips |
| R2-2201372 | Introduction of BCS4 and BCS5 | Xiaomi Communications, Samsung, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, OPPO, Huawei, HiSilicon, ZTE Corporation, Sanechips |
| R2-2201385 | Introduction of new FR2 CA bandwidth classes | Xiaomi Communications |
| R2-2201436 | Discussion on the DC location report for more than 2CC | Huawei, HiSilicon |
| R2-2201499 | Remaining issues to support R17 UL Tx switching enhancement | Huawei, HiSilicon, China Telecom, CATT |
| R2-2201500 | RRC configuration to support R17 UL Tx switching enhancements | Huawei, HiSilicon, China Telecom, CATT |
| R2-2201501 | Running CR to TS38.331 to support Tx switching enhancements | Huawei, HiSilicon, China Telecom, Apple, CATT |
| R2-2201502 | Further discussion on beam information of PUCCH SCell in PUCCH SCell activation (RAN1 LS) | Huawei, HiSilicon |
| R2-2201503 | Draft LS Reply on beam information of PUCCH SCell in PUCCH SCell activation procedure | Huawei, HiSilicon |
| R2-2201504 | Draft CR to TS38.321 for Beam information reporting via MAC CE for PUCCH SCell activation | Huawei, HiSilicon |
| R2-2201505 | Draft CR to TS38.331 for Beam information reporting via MAC CE for PUCCH SCell activation | Huawei, HiSilicon |
| R2-2201673 | Draft Reply LS on HO with PSCell from NR SA to EN-DC | MediaTek Inc. |
| R2-2201834 | Introduction of BCS4 and BCS5 | Xiaomi Communications, Samsung, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, OPPO, Huawei, HiSilicon, ZTE Corporation, Sanechips |
| R2-2201835 | Introduction of BCS4 and BCS5 | Xiaomi Communications, Samsung, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, OPPO, Huawei, HiSilicon, ZTE Corporation, Sanechips |
| R2-2201836 | Summary for email discussion [AT116bis-e][035][NR17] DC Location Reporting | Qualcomm Incorporated |
| R2-2201853 | Summary of [AT116bis-e][033][NR17] (Huawei) | Huawei, HiSilicon |
| R2-2201857 | Report of [AT116bis-e][039][NR17] RRM enh for HST (CMCC) | CMCC |
| R2-2201858 | Introduction of RRM enhancements for Rel-17 NR FR1 HST | CMCC, Ericsson |
| R2-2201859 | Introduction of RRM enhancements for Rel-17 NR FR1 HST | CMCC, Ericsson |
| R2-2201871 | Summary of [AT116bis-e][036][NR17] UL TX switching Enh (China Telecom) | China Telecom |
| R2-2201872 | Draft CR to TS 38.306 on UE capability for UL-MIMO coherence for Rel-17 Tx switching | China Telecom, Huawei, HiSilicon |
| R2-2201873 | RRC configuration to support R17 UL Tx switching enhancements | Huawei, HiSilicon, China Telecom, CATT |
| R2-2201901 | Summary of [AT116bis-e][041][NR17] HO with PSCell (MediaTek) | MediaTek |
| R2-2201902 | Reply LS on HO with PSCell from NR SA to EN-DC | RAN2 |
| R2-2201911 | The summary of [Offline-040][NR17] BCS4 and BCS5 (xiaomi) | xiaomi |
| R2-2201913 | Summary of [AT116bis-e][038][NR17] FR2 UL Gap (Apple) | Apple |
| R2-2201917 | Offline 037 on FR2 CA BW class | Nokia (Rapporteur) |
| R2-2201928 | Offline 037 on FR2 CA BW class | Nokia (Rapporteur) |
| R2-2201931 | [DRAFT] Reply LS on DC location for >2CC | Qualcomm Incorporated |
| R2-2201933 | Summary of [AT116bis-e][033][NR17] (Huawei)-Phase II | Huawei |
| R2-2201939 | Running CR to TS 38.306 to support Tx switching enhancements (UE capability) | China Telecom, Huawei, HiSilicon, Apple, CATT |
| R2-2201940 | Running CR to TS38.331 to support Tx switching enhancements (UE capability) | Huawei, HiSilicon, China Telecom, Apple, CATT |
| R2-2201945 | Reply LS to RAN2 on UL gap in FR2 RF enhancement (R4-2202419; contact: Apple) | RAN4 |
| R2-2201947 | Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure | RAN2 |
| R2-2201978 | Reply LS on DC location for >2CC | RAN2 |
| 8.24.2 | RAN1 led Items | |
| R2-2200294 | DSS and RA Procedure | Samsung Electronics Co., Ltd |
| R2-2201039 | RRC running CR for DSS | Ericsson |
| R2-2201040 | RAN2 impact in DSS WI | Ericsson |
| R2-2201396 | Discussion on Cross-Carrier Scheduling from sSCell to P(S)Cell | vivo |
| R2-2201618 | Remaining issues on cross-carrier scheduling from SCell to P(S)Cell | Huawei, HiSilicon |
| R2-2201698 | Summary of [AT116bis-e][042][NR17] DSS (Ericsson) | Ericsson |
| R2-2201946 | RRC running CR for DSS | Ericsson |
| 8.24.3 | Other | |
| R2-2200061 | Response to reply LS on UAC enhancements and system information extensions for minimization of service interruption (C1-217156; contact: Nokia) | CT1 |
| R2-2200135 | LS on Duplicate Measurements when SCell is a Neighbor Cell (R5-217991; contact: Qualcomm) | RAN5 |
| R2-2200151 | Reply LS on LS on MINT functionality for Disaster Roaming (S3-214416; contact: LGE) | SA3 |
| R2-2200154 | LS Reply on security protection of RRCResumeRequest message (S3-214539; contact: NTT DOCOMO) | SA3 |
| R2-2200155 | Reply LS to CT3 Questions and Feedback on EVEX (S4-211647; contact: Qualcomm) | SA4 |
| R2-2201083 | Response LS on duplicated measurements for SCell | Nokia, Nokia Shanghai Bell |
| R2-2201084 | On duplicated measurement results when SCell is a neighbour | Nokia, Nokia Shanghai Bell |
| R2-2201141 | Further discussion on support of MINT feature in AS | Lenovo, Motorola Mobility |
| R2-2201142 | Introduction of MINT feature in TS 38.306 | Lenovo, Motorola Mobility |
| R2-2201143 | Introduction of MINT feature in TS 36.306 | Lenovo, Motorola Mobility |
| R2-2201161 | Clarifications on security protection of RRCResumeRequest message | Ericsson |
| R2-2201162 | [Draft] Reply LS on security protection of RRCResumeRequest message | Ericsson |
| R2-2201437 | Introduction of MINT for LTE | Huawei, HiSilicon |
| R2-2201471 | Resolving open isseus for supporting disaster roaming | LG Electronics |
| R2-2201506 | Security protection on RRCResumeRequest message (SA3 LS) | Huawei, HiSilicon |
| R2-2201550 | Introduction of MINT | Ericsson |
| R2-2201551 | Introduction of MINT | Ericsson |
| R2-2201552 | Remaining issues for MINT | Ericsson |
| R2-2201840 | Report from [AT116bis-e][043][NR17] MINT (Ericsson) | Ericsson |
| R2-2201841 | Reply LS on UAC enhancements and system information extensions for minimization of service interruption | RAN2 |
| R2-2201842 | Introduction of MINT | Ericsson |
| R2-2201843 | Introduction of MINT | Ericsson |
| R2-2201844 | Introduction of MINT | Ericsson |
| R2-2201845 | Introduction of MINT | Ericsson |
| R2-2201846 | Introduction of MINT | Ericsson |
| R2-2201847 | Introduction of MINT | Ericsson |
| R2-2201848 | Introduction of MINT | Ericsson |
| R2-2201849 | Introduction of MINT | Ericsson |
| R2-2201863 | Summary of [AT116bis-e][044][NR17] RRC resume security (NTT DOCOMO) | NTT DOCOMO, INC. |
| R2-2201864 | Reply LS on security protection of RRCResumeRequest message | RAN2 |
| R2-2201924 | Response LS on duplicated measurements for SCell | RAN2 |
| 9.0.2 | Feature Lists and UE capabilities | |
| R2-2200090 | LS on updated Rel-17 RAN1 UE features list for LTE (R1-2112901; contact: NTT DOCOMO, AT&T) | RAN1 |
| 9.1.1 | Organizational | |
| R2-2200027 | [Running CR] Introduction of NB-IoT/eMTC Enhancements | Qualcomm Incorporated |
| R2-2200029 | Running CR: Introduction of additional enhancements for NB-IoT and eMTC | ZTE Corporation, Sanechips |
| R2-2200048 | Running CR: Introduction of Rel-17 enhancements for NB-IoT and eMTC | Huawei |
| R2-2200058 | [Running CR] Introduction of NB-IoT/eMTC Enhancements | Nokia |
| R2-2200093 | LS on channel quality reporting for NB-IoT (R1-2112971; contact: Huawei) | RAN1 |
| R2-2201788 | Running CR: Introduction of Rel-17 enhancements for NB-IoT and eMTC | Huawei |
| R2-2201789 | Running CR: Introduction of Rel-17 enhancements for NB-IoT and eMTC | Huawei |
| R2-2201790 | [Running CR] Introduction of NB-IoT/eMTC Enhancements | Qualcomm Incorporated |
| R2-2201791 | [Running CR] Introduction of NB-IoT/eMTC Enhancements | Nokia |
| R2-2201792 | Running CR: Introduction of additional enhancements for NB-IoT and eMTC | ZTE Corporation, Sanechips |
| R2-2201796 | [311][NBIOT/eMTC R17] Capabilities open issues (Huawei) | Huawei, HiSilicon |
| R2-2202047 | RAN2 agreements for Rel-17 NB-IoT and LTE-MTC | Document Rapporteur (Ericsson) |
| 9.1.2 | NB-IoT neighbor cell measurements and corresponding measurement triggering before RLF | |
| R2-2200028 | Report of [Post116-e][310][NBIOT/eMTC] RLF measurements | Qualcomm Incorporated |
| R2-2200675 | On remaining issues for connected mode measurements for RLF | Nokia, Nokia Shanghai Bells |
| R2-2200681 | Remaining FFSs on connected mode measurement | ZTE Corporation, Sanechips |
| R2-2201020 | Consideration on open issues for neighbour cell measurement in RRC connected state | Qualcomm Incorporated |
| R2-2201077 | Discussion on connected mode measurement in NB-IoT | Ericsson |
| R2-2201534 | Support of Early rLF | THALES |
| R2-2201793 | Report of [AT116bis-e][302][NBIOT/eMTC R17] RLF Measurements (Qualcomm) | Qualcomm Incorporated |
| R2-2201794 | [Post116bis-e][309][NBIOT/eMTC R17] RLF measurements open issues (Qualcomm) | Qualcomm Incorporated |
| 9.1.3 | NB-IoT carrier selection based on the coverage level, and associated carrier specific configuration | |
| R2-2200030 | Report of [Post116-e][311] NB-IoT carrier selection | ZTE Corporation, Sanechips |
| R2-2200633 | The remaining issues on enhanced paging carrier selection | Spreadtrum Communications |
| R2-2200676 | Further details on coverage level based paging carrier selection | Nokia, Nokia Shanghai Bells |
| R2-2200682 | Remaining FFSs on CEL-based paging carrier selection | ZTE Corporation, Sanechips |
| R2-2200866 | Discussion on the issue for Random Access on multicarrier for NB-IoT | CMCC |
| R2-2200867 | Solution for random access issue on multiCarrier in NB-IoT | CMCC |
| R2-2200868 | Solution for random access issue on multiCarrier in NB-IoT | CMCC |
| R2-2200922 | Discussion on details of paging carrier selection | MediaTek Inc. |
| R2-2201021 | Paging carrier selection with hysteresis | Qualcomm Incorporated |
| R2-2201022 | Signalling for coverage-based paging carrier selection | Qualcomm Incorporated |
| R2-2201076 | Remaining issues of carrier selection | Ericsson |
| R2-2201786 | Report of [AT116bis-e][301][NBIOT/eMTC R17] Carrier selection (ZTE) | ZTE (email discussion rapporteur) |
| R2-2201795 | Report of [Post116bis-e][310][NBIOT/eMTC R17] Carrier Selection open issues (ZTE) | ZTE (email discussion rapporteur) |
| 9.1.4 | Other | |
| R2-2200677 | On thje open issues for 16QAM for NB-IoT | Nokia, Nokia Shanghai Bells |
| R2-2200683 | Remaining FFSs on 16QAM for NB-IoT and 1736bits TBS for eMTC | ZTE Corporation, Sanechips |
| R2-2201078 | Support of 16-QAM for unicast in UL and DL in NB-IoT | Ericsson |
| R2-2201448 | Introduction of Rel-17 enhancements for NB-IoT and eMTC | Huawei, HiSilicon |
| R2-2201449 | CQI reporting for 16QAM DL | Huawei, HiSilicon |
| R2-2201450 | UE capabilities and FDD/TDD, EPC/5GC differentiation | Huawei, HiSilicon |
| R2-2201787 | [AT116bis-e][303][NBIOT/eMTC R17] UE Capabilities (Huawei) | Huawei |
| R2-2201797 | Report on [Post116bis-e][312][NBIOT/eMTC R17] Other open issues (Ericsso | Ericsson |
| 9.2.1 | Organizational | |
| R2-2200064 | Reply LS on EPS support for IoT NTN in Rel-17 (C1-217258; contact: MediaTek) | CT1 |
| R2-2200084 | LS on GNSS Validity duration for IoT NTN (R1-2112848; contact: MediaTek) | RAN1 |
| R2-2200146 | Reply LS on EPS support for IoT NTN in Rel-17 (S2-2109344; contact: MediaTek) | SA2 |
| R2-2201451 | Running CR - Support of Non-Terrestrial Network in NB-IoT and eMTC | Huawei |
| R2-2201452 | Extended NAS timers for IOT NTN | Huawei, HiSilicon |
| R2-2201602 | Discussion on IoT NTN reply LS to CT1 on extended NAS supervision timers | Ericsson |
| R2-2201603 | Draft reply LS to CT1 on IoT NTN extended NAS supervision timers | Ericsson |
| R2-2201619 | Discussion on reply on extended NAS supervision timers for IoT NTN | Nokia, Nokia Shanghai Bell |
| R2-2201769 | Running CR - Support of Non-Terrestrial Network in NB-IoT and eMTC | Huawei |
| R2-2201770 | Report of [Post-116bis-e][046][IoT-NTN] 36.331 open issues | Huawei |
| R2-2201951 | Reply LS on IoT NTN extended NAS supervision timers at satellite access | RAN2 |
| R2-2202012 | Report of [Post-116bis-e][088][IoT-NTN] 36304 open issues | Ericsson |
| R2-2202013 | IoT NTN 36304 Running CR | Ericsson |
| R2-2202051 | Stage-3 running CR for TS 36.321 for Rel-17 IoT-NTN | MediaTek |
| 9.2.2 | Support of Non continuous coverage | |
| R2-2200217 | Discussion on remaining issues on Non continuous coverage | Intel Corporation |
| R2-2200252 | Discussion on the support of discontinuous coverage for IoT over NTN | OPPO |
| R2-2200440 | Details on the support of the discontinuous coverage | Qualcomm Incorporated |
| R2-2200623 | On Discontinuous coverage in IoT-NTN | MediaTek Inc. |
| R2-2200634 | Discussion on the remaining issue of non-continuous coverage | Spreadtrum Communications |
| R2-2200651 | Discussion on the support of discontinuous coverage for IoT over NTN | Transsion Holdings |
| R2-2200691 | Discussion on supporting non-continuous coverage | CATT |
| R2-2200694 | Remaining FFSs on discontinuous coverage in IoT NTN | ZTE Corporation, Sanechips |
| R2-2200713 | Discussion on discontinuous coverage | Xiaomi |
| R2-2200768 | Prediction of coverage discontinuity for IoT NTN | Lenovo, Motorola Mobility |
| R2-2200769 | Enhancement for idle UE power saving in discontinuous coverage | Lenovo, Motorola Mobility |
| R2-2200850 | Discussion on open issues for support of Non continuous coverage | CMCC |
| R2-2201009 | Discussion on remaining aspects of discontinuous coverage in IoT NTN | Nokia, Nokia Shanghai Bell |
| R2-2201017 | On satellite ephemeris information types for discontinuous coverage in IoT-NTN | Sateliot, Gatehouse |
| R2-2201181 | Support of discontinuos coverage | Apple |
| R2-2201453 | Discussion on non continuous coverage | Huawei, HiSilicon |
| R2-2201546 | Support of Discontinuous Coverage for IoT-NTN | Interdigital, Inc. |
| R2-2201599 | Discontinuous coverage in IoT NTN | Ericsson |
| R2-2201620 | Support for Discontinuous Coverage NB IoT NTN | Rakuten Mobile, Inc |
| R2-2201688 | [Pre116bis][014][IOT-NTN] Summary of 9.2.2 Support of Non continuous coverage (MediaTek) | MediaTek Inc. |
| 9.2.3 | User Plane Impact | |
| R2-2200253 | Discussion on UP impact for IoT over NTN | OPPO |
| R2-2200692 | Discussion on TA information reporting for IoT NTN | CATT |
| R2-2200698 | Remaining FFSs on UP in IoT NTN | ZTE Corporation, Sanechips |
| R2-2200878 | Remaining issues on UP aspects for IoT-NTN | CMCC |
| R2-2201010 | On User Plane left issues for IoT NTN | Nokia, Nokia Shanghai Bell |
| R2-2201454 | User plane for IOT NTN | Huawei, HiSilicon |
| R2-2201631 | User plane aspects of NB-IoT and LTE-M in NTNs | Ericsson |
| R2-2201655 | [Pre116bis][015][IOT-NTN] Summary of 9.2.3 User Plane Impact (OPPO) | OPPO |
| 9.2.4 | Control Plane Impact | |
| R2-2200218 | Discussion on new barring bit | Intel Corporation |
| R2-2200254 | Discussion on CP impact for IoT over NTN | OPPO |
| R2-2200273 | RAN2 aspects of UL sync validity timer and GNSS position validity | Xiaomi |
| R2-2200441 | UL synchronization validity timer in RRC_CONNECTED | Qualcomm Incorporated |
| R2-2200442 | Discussion on the GNSS validity duration | Qualcomm Incorporated |
| R2-2200622 | On GNSS Validity Duration in IoT-NTN | MediaTek Inc. |
| R2-2200624 | Validity Timer Expiry and Synchronization Loss in IoT-NTN | MediaTek Inc. |
| R2-2200673 | Further discussion on remaining control plane issues for IoT-NTN control plane | Nokia, Nokia Shanghai Bells |
| R2-2200693 | Discussion on the open issues of CP impact | CATT |
| R2-2200699 | Remaining FFSs on CP in IoT NTN | ZTE Corporation, Sanechips |
| R2-2200714 | Discussion on RRC idle mode issues for IoT NTN | Xiaomi |
| R2-2200770 | Serving and neighboring ephemeris in system information for IoT NTN | Lenovo, Motorola Mobility |
| R2-2200871 | Remaining Issues of CP Impact of IoT over NTN | CMCC |
| R2-2201182 | Provision of ephemeris | Apple |
| R2-2201197 | Soft TAC update | NEC Telecom MODUS Ltd. |
| R2-2201455 | Control plane for IOT NTN | Huawei, HiSilicon |
| R2-2201547 | Location Reporting in RRC_CONNECTED | Interdigital, Inc. |
| R2-2201548 | TAC validity timer | Interdigital, Inc. |
| R2-2201600 | Control plane aspects of IoT NTN | Ericsson |
| R2-2201660 | [Pre116bis][016][IOT-NTN] Summary of 9.2.4 Control Plane Impact (Huawei) | Huawei |
| R2-2201860 | Report of [046][IoT-NTN] RRC Misc | Huawei, HiSilicon |
| R2-2201952 | LS on UE providing Location Information for NB-IoT | RAN2 |
| R2-2201953 | LS on security concerns for UE providing Location Information for NB-IoT | RAN2 |
| R2-2201954 | Report on discussion of LSes on UE location Info for NB-IoT | Ericsson |
| R2-2201957 | LS on UE providing Location Information for NB-IoT | RAN2 |
| R2-2201958 | LS on security concerns for UE providing Location Information for NB-IoT | RAN2 |
| 9.2.5 | UE Capabilities | |
| R2-2200255 | Discussion on IoT NTN UE capabilities | OPPO |
| R2-2200443 | Discussion on UE capabilities | Qualcomm Incorporated |
| R2-2200674 | Analysis on IoT-NTN UE capability requirements | Nokia, Nokia Shanghai Bells |
| R2-2200702 | Consideration on UE capability report for IoT NTN | ZTE Corporation, Sanechips |
| R2-2200875 | RAN2 UE Feature List for IoT NTN | CMCC |
| R2-2201456 | Discussion on UE capability | Huawei, HiSilicon |
| R2-2201601 | IoT NTN capabilities | Ericsson |
| R2-2201981 | Discussion on [AT116bis-e][047][IoT-NTN] UE capabilities | Nokia, Nokia Shanghai Bell |
| 9.3 | EUTRA R17 Other | |
| R2-2200153 | LS on LTE User Plane Integrity Protection (S3-214462; contact: Vodafone) | SA3 |
| R2-2200209 | Introduction of new bands and bandwidth allocation for LTE-based 5G terrestrial broadcast | Qualcomm Incorporated |
| R2-2200368 | On introducing height information reporting in MDT reports | KDDI Corporation, Ericsson |
| R2-2200370 | On introducing height information reporting in MDT reports | KDDI Corporation, Ericsson |
| R2-2200371 | On introducing height information reporting in MDT reports | KDDI Corporation, Ericsson |
| R2-2201513 | Draft CR to TS 36.331 to support UP IP for EPC connected architectures using NR PDCP | Huawei, HiSilicon, Vodafone |
| R2-2201514 | Draft CR to TS 38.331 to support UP IP for EPC connected architectures using NR PDCP | Huawei, HiSilicon, Vodafone |
| R2-2201515 | Draft CR to TS 36.300 to support UP IP for EPC connected architectures using NR PDCP | Huawei, HiSilicon, Vodafone |
| R2-2201516 | Draft CR to TS 37.340 to support UP IP for EPC connected architectures using NR PDCP | Huawei, HiSilicon, Vodafone |
| R2-2201517 | Draft CR to TS 38.323 to support UP IP for EPC connected architectures using NR PDCP | Huawei, HiSilicon, Vodafone |
| R2-2201525 | Discussion on LTE User Plane Integrity Protection (SA3 LS) | Huawei, HiSilicon |
| R2-2201621 | Proposal to respond to SA3 LS S3-214462 (R2-2200153) on LTE User Plane Integrity Protection | VODAFONE Group Plc |
| 9.4 | NR and EUTRA Inclusive language | |
| R2-2200159 | Reply LS on Inclusive language for ANR (S5-216197; contact: Huawei) | SA5 |
| 10.1 | Session on LTE legacy, Mobility, DCCA, Multi-SIM and RAN slicing | |
| R2-2201661 | Report from session on LTE legacy, 71 GHz, DCCA, Multi-SIM and RAN slicing | Vice Chairman (Nokia) |
| 10.2 | Session on R17 NTN and RedCap | |
| R2-2201662 | Report from Break-Out Session on R17 NTN, RedCap and CE | Vice Chairman (ZTE) |
| 10.3 | Session on eMTC | |
| R2-2201663 | Report eMTC breakout session | Session chair (Ericsson) |
| 10.4 | Session on R17 Small data and URLLC/IIOT | |
| R2-2201664 | Report for Rel-17 Small data and URLLC/IIoT | Session chair (InterDigital) |
| 10.5 | Session on positioning and sidelink relay | |
| R2-2201665 | Report from session on positioning and sidelink relay | Session chair (MediaTek) |
| 10.6 | Session on SON/MDT | |
| R2-2201666 | Report from SON/MDT session | Session chair (CMCC) |
| 10.7 | Session on NB-IoT | |
| R2-2201667 | Report NB-IoT breakout session | Session chair (Huawei) |
| 10.8 | Session on LTE V2X and NR SL | |
| R2-2201668 | Report from session on LTE V2X and NR SL | Session chair (Samsung) |